I like where this could go, but basing it on calories isn't particularly useful. 300 calories of garbage (or corn syrup if you will) is still eating garbage.
Farther out, the plan is to allow users to conduct structured searches along all dimensions of menu items - macro-nutrients, sodium, etc. Due to the limitations of one of the APIs I'm using, I can only support a calorie parameter in queries for now. Note that once you drill into a particular menu item, you are provided with in-depth nutritional data like carbohydrates, protein, and fat.
In the meantime, the hope is that calories are useful as a jumping off point when it comes to discovering healthy dishes nearby, and as I mentioned before you can see the full nutritional info by clicking on a particular item.