Skip to main content
Glama
Sign In

Foodbe

by io.github.bleemohr
OverviewDiscussionsAdmin

foodbe_meal_plan

Read-only

Call this when a user asks for a meal plan or for what to eat over a number of days. Builds a plan of 1 to 7 days from Foodbe's recipes, within an optional dollar budget for the whole plan, filtered by the diet and allergies you send. Returns outcome "served" with the plan and its insight: the taste the plan is missing, the food group it is short on, the health roles it covers, and its cheapest, priciest and quickest meal. Every line comes from Foodbe's stored data, never from a model. If no plan can be built, it returns outcome "not_found".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "foodbe_meal_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional number of days, from 1 to 7.
dietNoOptional diet to filter by, for example Vegan.
budgetNoOptional most the whole plan may cost, in US dollars.
allergiesNoOptional allergens to leave out, for example Peanuts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly, non-destructive and closed-world, yet the description still adds real behavioral context: the plan is bounded to 1-7 days, budget applies to the whole plan, results are filtered by diet and allergies, and the content of the returned insight is enumerated. It also discloses the failure mode (outcome "not_found" if no plan can be built) and the provenance guarantee ('Every line comes from Foodbe's stored data, never from a model').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger, then behavior, then return shape, then the provenance note, then the failure case — five tight sentences with no redundancy. Every sentence carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description fully covers the return contract: outcome values 'served' and 'not_found' plus the four insight components. Combined with the annotations and complete parameter documentation, nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four optional parameters are already documented, establishing a baseline of 3. The description mainly restates them in prose (day range, whole-plan dollar budget, diet and allergy filtering) without adding format, precedence, or interaction details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource ('Builds a plan of 1 to 7 days from Foodbe's recipes') and states the user request that maps to it ('a meal plan or ... what to eat over a number of days'). That scope is distinct from sibling-looking tools such as recipe lookup or grocery-list generation, so an agent can choose this without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit invocation trigger ('Call this when a user asks for a meal plan or for what to eat over a number of days'), which is stronger than implied usage. It stops short of a 5 because it names no excluded cases or alternative tools for adjacent needs (single-recipe lookup, comparison, grocery list).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Foodbe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources