Skip to main content
Glama

delete_workout_plan

Destructive

Delete a workout 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_workout_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 declare destructiveHint=true, so the description earns credit for going further: it states the deletion is permanent ('for good'), that the client loses access, and that it is confirm-gated. It does not say whether assignments/history are cascaded or whether deletion is recoverable, which are the remaining behavioral gaps.

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 destructive nature and gating front-loaded before the softer alternative recommendation. Every clause carries distinct 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 annotations covering safety, the description supplies permanence, client impact, gating, and a decision rule. It lacks only cascade/restore semantics and any guidance on how to obtain a valid planId.

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?

The 'confirm' parameter is already fully documented in the schema, and 'confirm-gated' in the description only restates it. The 'planId' parameter has no schema description at 50% coverage, and the description supplies no format or sourcing guidance for it beyond implying it identifies the workout plan.

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 ('Delete a workout plan') and adds distinguishing scope: deletion is permanent and confirm-gated. It does not explicitly contrast with delete_workout_plan_template or delete_plan, but the phrase 'prefer editing' points an agent toward the update sibling.

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?

It gives a clear decision rule — only use this when the coach clearly wants the plan gone, otherwise edit instead. The alternative is described by intent ('editing') rather than by tool name, so the agent must map it to update_workout_plan itself, but the when-not condition is explicit.

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.