Skip to main content
Glama

delete_custom_exercise

Destructive

Delete one of the coach's own custom exercises (only items with custom: true and editable: true in browse_exercise_catalog). Existing plans keep their copy. (confirm-gated: previews until confirm: true)

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond that: the confirm-gated preview step and the non-cascading behavior ("existing plans keep their copy"). It does not say what the preview returns or what error occurs for a non-editable id.

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?

Three short clauses, front-loaded with the verb and resource, then precondition, side effect, and gating. Efficient, though the stacked parentheticals make it slightly denser than necessary.

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, it covers eligibility, side-effect scope, and the confirm preview gate. Minor remaining gaps are the shape of the preview response and failure behavior on ineligible ids.

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%: `confirm` is fully documented in the schema, while `id` has only minLength:1. The description partially compensates by implying the id comes from browse_exercise_catalog and by reinforcing the confirm gate, but it never states the id's format or origin explicitly.

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

Purpose5/5

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

Specific verb+resource ("Delete ... custom exercises") with an explicit ownership scope ("the coach's own") and a machine-checkable precondition tied to browse_exercise_catalog flags. An agent can immediately tell this apart from create_custom_exercise/update_custom_exercise and knows which items are eligible.

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?

States the precondition for use (only items with custom: true and editable: true in browse_exercise_catalog), which implicitly excludes read-only/catalog exercises and points the agent at the discovery tool first. It stops short of explicitly naming update_custom_exercise as the alternative when the coach wants to modify rather than remove.

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.