Skip to main content
Glama

update_diet_plan_template

Edit an existing diet plan template (confirm-gated). Only send the fields that change.

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": "update_diet_plan_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
goalNo
tagsNo
mealsNo
titleNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
difficultyNo
visibilityNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so safety basics are covered. The description adds genuinely new behavioral context by flagging the confirm gate, but says nothing about what happens on a non-existent id, whether omitted fields are preserved versus cleared, or any permission requirements.

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?

Two short sentences, front-loaded with the action and resource, with no filler. It is arguably too terse given nine parameters, but no sentence is wasted.

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

Completeness3/5

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

For a nine-parameter mutation with 11% schema coverage and no output schema, the description is thin: it does not explain the required id, the shape of the meals payload, or what the preview response looks like. The confirm-gate and partial-update notes are the right minimum, but more parameter grounding is needed.

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 only 11% (only 'confirm' is documented), so the schema carries little meaning for the other eight parameters. The description partially compensates by establishing partial-update semantics ('only send the fields that change'), which tells the agent omitted fields are not required, but it says nothing about id, meals, visibility, tags, or the enum fields.

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 states a specific verb and resource ('Edit an existing diet plan template'), which clearly separates it from create/delete/get siblings by name convention. It does not explicitly name which sibling to use for full replacement or for plan instances versus templates, so it stops short of 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?

'Only send the fields that change' gives real usage guidance for a patch-style call, and '(confirm-gated)' hints at the two-step flow. However, there is no explicit statement of when to use this instead of update_diet_plan or create_diet_plan_template, leaving the template-vs-instance distinction to inference.

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.