Skip to main content
Glama

update_diet_plan

Edit an existing diet plan (confirm-gated). Pass planId plus only the fields to change. meals, if given, REPLACES the whole meal list — send the full intended list. Each meal follows the create_diet_plan shape (name, scheduledTime 'HH:mm', order, days, section, calories, macros, description, ingredients).

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

Input Schema

NameRequiredDescriptionDefault
mealsNo
titleNo
planIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
endDateNo
startDateNoYYYY-MM-DD
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive mutation with no open-world access. The description adds genuinely new behavior beyond that: the confirm gate and, critically, the destructive-in-effect semantics of 'meals REPLACES the whole meal list — send the full intended list', which an agent could not infer from annotations or schema. It stops short of stating permission requirements or what the preview response contains.

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 core action and the patch rule, then spends the remaining space on the highest-risk parameter (meals replacement). The parenthetical field inventory for meals is long but earns its place by pointing the agent at the authoritative shape; nothing is filler.

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 confirm-gated mutation with a deeply nested meals array and no output schema, the description covers the two things most likely to cause a bad call: the confirm gate and full-list replacement. It is incomplete on the scalar fields (title, description, startDate, endDate) and on what a preview versus a committed update returns, which is a meaningful gap for a mutation tool at 29% schema coverage.

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 29%, so the description must compensate, and it partially does: it establishes planId as required-plus-fields-to-change, explains the replace semantics of meals, and names the meal shape and the 'HH:mm' format for scheduledTime. It says nothing about title, description, startDate, or endDate, leaving four of the seven parameters without added meaning anywhere.

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?

States a specific verb and resource: 'Edit an existing diet plan', with the '(confirm-gated)' qualifier making it clear this is a mutation of an already-existing plan rather than creation. It does not explicitly distinguish itself from update_diet_plan_template or create_diet_plan, but 'existing diet plan' is specific enough for an agent to tell it apart from the create path.

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?

Provides a concrete invocation rule -- 'Pass planId plus only the fields to change' -- which is real patch-semantics guidance. However, it never states when to prefer this over create_diet_plan or update_diet_plan_template, and the confirm-gate flow (preview vs execute) is only implied by 'confirm-gated' rather than explained as an intended workflow.

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.