Retrieve a saved meal plan by its UUID to access your previously planned meals.
Read a saved meal plan by its generated UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| plan_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| recipes | Yes | ||
| plan_name | Yes | ||
| created_at | Yes | ||
| total_recipes | Yes |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's 'Read' aligns with them. It adds no extra behavioral context (e.g., errors, response format), but the annotations cover safety, so a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no unnecessary words. It directly states the action and resource, earning its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter and has an output schema and annotations covering safety. The description is sufficient for an agent to call it correctly; nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description specifies that plan_id is a 'generated UUID', adding semantic meaning beyond the schema's length constraints. Since schema coverage is 0%, this helps the agent understand the expected format, though it is minimal.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Read' and the resource 'saved meal plan', and identifies the identifier as a 'generated UUID'. This distinguishes it from siblings like create_meal_plan (write) and search_recipes (search).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used when you have a UUID and want to read a specific meal plan, providing clear context. It doesn't explicitly mention alternatives or exclusions, but the purpose is unambiguous given the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.