Skip to main content
Glama

get_diet_plan

Read-only

Full detail of one client diet plan: every meal (time, section, calories, macros, ingredients, notes) and the original PDF's text when the plan came from a coach's PDF. Pass the plan _id from list_diet_plans. If document is present with no exercises/meals, the plan IS the coach's PDF (shared as-is): document.text is what the PDF says. A null document.text means the PDF is scanned or unreadable — tell the coach to open the plan on the web and use "Turn into a trackable plan" so it can be read and edited.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "planId": "<planId>"
    },
    "name": "get_diet_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this readOnly and closed-world, and the description goes well beyond that: it explains the PDF-origin plan shape, the meaning of a populated `document` with empty meals/exercises, and that a null `document.text` indicates a scanned PDF. It even prescribes the recovery path ('Turn into a trackable plan'), which is real behavioral context an agent cannot get from structured fields.

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

Conciseness4/5

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

Front-loads the return shape, then the id source, then the PDF edge cases in a logical progression. The closing remediation sentence is long but applies to a real failure mode, so it earns its place; slight density cost only.

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?

There is no output schema, so the description carries the return-value burden, and it does: it enumerates meal fields and describes `document.text` semantics including the null case. For a single-parameter read tool, nothing an agent needs to invoke or interpret it correctly is missing.

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

Parameters4/5

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

Schema coverage is 0% and the single `planId` param has no description, but the description compensates by naming the parameter (`_id`) and its source (from list_diet_plans), so the agent knows what value to supply. It does not state the id format beyond that, keeping it short of a 5.

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?

States a specific verb and resource ('Full detail of one client diet plan') and enumerates the returned fields (time, section, calories, macros, ingredients, notes), which distinguishes it from list_diet_plans, the tool it explicitly routes to for the _id.

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?

Gives explicit entry-point guidance: 'Pass the plan _id from list_diet_plans,' so the agent knows the prerequisite call. It also prescribes an action for the unreadable-PDF case, though it does not contrast with get_diet_plan_template or state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.