Skip to main content
Glama

mywhoosh_delete_workout

Delete a custom cycling workout by ID; if a training plan uses it, nothing is removed unless force is true.

Instructions

Delete a custom cycling workout by id (see mywhoosh_list_workouts).

If the workout is used by a training plan, nothing is deleted unless force=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": {
      "workout_id": "<workout_id>"
    },
    "name": "mywhoosh_delete_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the important conditional behavior that the call becomes a no-op unless force=True when the workout belongs to a training plan. It omits irreversibility, what "force" deletes (workout only, or plan references too), permission needs, and failure behavior for an unknown 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?

Two short sentences, front-loaded with the action and immediately followed by the blocking condition; nothing is padded. The parenthetical pointer to the listing tool is slightly awkward but functional.

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 no annotations, this covers purpose, id source, and the key partial-failure guard. Remaining gaps (irreversibility, not-found behavior, return value) are modest but real for a delete operation.

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 0%, so the description must compensate. It conveys force's effect (bypasses the in-use guard) and that workout_id comes from mywhoosh_list_workouts, but leaves force's default of false, its exact interaction with plan references, and workout_id's type/range unstated.

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 ("Delete a custom cycling workout by id") and scopes it to custom workouts, which separates it from create/update/schedule siblings. It stops short of explicitly contrasting with mywhoosh_unschedule_workout, which is the operationally adjacent alternative.

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?

Gives useful entry context (get the id from mywhoosh_list_workouts) and states the precondition that a plan-referenced workout requires force=True. It never says when to prefer unscheduling over deleting or when deletion should be avoided, so the alternative-selection guidance is only implied by the sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.