Skip to main content
Glama

get_diet_plan_template

Read-only

Full detail of one diet plan template, including every meal.

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": {
      "id": "<id>"
    },
    "name": "get_diet_plan_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description contributes one meaningful behavioral detail — the response is the complete template with all meals, not an abbreviated record — but says nothing about missing-ID behavior, sizing, or what fields accompany the meals, and there is no output schema to fill that gap.

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?

One short sentence, front-loaded with the core action and immediately followed by the distinguishing detail about meals. No filler, hedging, or redundant restatement of the tool name.

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

Completeness4/5

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

For a simple single-record read with one required parameter and annotations covering the safety profile, the definition is nearly sufficient — the agent knows exactly what it retrieves. The remaining gap is the unexplained 'id' source/format and the shape of the returned detail, which matters slightly more given there is no output schema.

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?

There is a single required 'id' parameter with 0% schema description coverage, so the schema itself gives no semantics. The description only indirectly conveys that the id selects one template; it never states the identifier type, source (where to obtain it), or validity expectations, leaving the one parameter under-explained.

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

Purpose4/5

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

The description names a specific verb and resource — fetch the full detail of a single diet plan template — and adds a scope cue ('including every meal') that distinguishes it from a summary/list view. It does not explicitly name the sibling it replaces (list_diet_plan_templates) or how it differs from get_diet_plan, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: 'one template' and 'full detail' hint that this is the tool for a single-record deep read rather than a listing, but there is no explicit when-to-use statement, no prerequisite, and no named alternative the agent should pick instead.

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.