Skip to main content
Glama

Remove a program ladder

remove_program_ladder
DestructiveIdempotent

Removes a ladder from the athlete's custom program. Its progress is kept and comes back if the ladder does. Forks a preset first.

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": {
      "exerciseId": "<exerciseId>"
    },
    "name": "remove_program_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
exerciseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is covered; the description adds genuinely non-obvious behavior beyond that: progress is retained and restored if the ladder is re-added, and a preset program is forked first. What it omits is whether the fork is a side effect the caller should expect or an external artifact, and there is no mention of error behavior.

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 sentences, front-loaded with the action, with no filler. However, 'Forks a preset first' is terse to the point of ambiguity about what is forked and when, costing structure clarity.

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 one-parameter destructive mutation with no output schema, the description covers the essential lifecycle (removed but recoverable) and a side effect. It is still incomplete on the parameter's meaning and the fork's implications, which an agent needs to call and interpret correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, and the description never addresses it. The parameter is named 'exerciseId' while the tool removes a 'ladder', and that non-obvious mapping is left entirely unexplained.

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: 'Removes a ladder from the athlete's custom program.' This is concrete enough to distinguish from sibling removers such as remove_program_day or remove_program_goal, though it does not explicitly name them.

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?

Usage is only implied: the reader infers you call this when you want a ladder gone from a custom program. There is no explicit when-not guidance, no prerequisites, and no stated alternative (e.g., what to use to remove an entire program day containing ladders).

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.

Resources