Skip to main content
Glama

delete_diet_plan

Destructive

Delete a diet plan for good (confirm-gated). The client loses access to it — prefer editing unless the coach clearly wants it gone.

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

Input Schema

NameRequiredDescriptionDefault
planIdYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds the consequence (the client loses access) and the irreversibility ("for good"). The confirm-gating mention duplicates the schema's own parameter description rather than adding new information.

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?

Two short sentences, zero padding, with the permanence and gating stated first and the usage steer second. Nothing could be removed without losing information.

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 two-parameter destructive tool with no output schema and full annotation coverage, the description supplies the key missing context: permanence, downstream effect on the client, and a preference for the non-destructive path. Only the planId parameter's meaning is left entirely to the 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?

Schema coverage is 50%: the confirm parameter is fully documented in the schema, while planId is undocumented in both places. The description's "confirm-gated" phrasing reinforces but does not extend the schema, so this sits at the baseline.

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?

"Delete a diet plan for good" states a specific verb and resource plus the permanence qualifier, and "prefer editing unless..." implicitly contrasts it with update_diet_plan. It stops short of naming the sibling tool, but an agent can still tell this is the destructive counterpart to editing.

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 a clear decision rule: edit instead of deleting unless the coach clearly wants the plan gone. That is real when-to-use/when-not guidance, though it references "editing" generically rather than pointing at a specific 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.