Skip to main content
Glama

mywhoosh_unschedule_workout

Remove a scheduled workout from your MyWhoosh calendar by task ID without deleting the workout itself.

Instructions

Remove a calendar entry by task_id (from mywhoosh_list_scheduled_workouts). The workout itself stays.

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": {
      "task_id": "<task_id>"
    },
    "name": "mywhoosh_unschedule_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It usefully states that only the calendar entry is removed and the workout remains, but it omits behavior for invalid task_id, idempotency, permissions, and whether the removal is reversible.

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, front-loaded with the action and identifier, then the key side effect. There is no filler or redundant wording.

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 single-parameter mutation with no annotations or output schema, the definition covers purpose, parameter source, and the main side effect. It stops short of failure/reversibility details, but those are the only notable omissions.

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

Parameters4/5

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

Schema coverage is 0% and the only parameter is otherwise undocumented, so the description's pointer to mywhoosh_list_scheduled_workouts is important: it tells the agent where to obtain a valid task_id. It does not describe the ID format, but the source is enough to compensate for most of the coverage gap.

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?

The description names a specific mutation, 'Remove a calendar entry,' and the resource, 'calendar entry,' plus the identifier to use. It explicitly separates this from deleting the underlying workout by saying 'The workout itself stays,' so an agent can distinguish it from mywhoosh_delete_workout.

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 identifies mywhoosh_list_scheduled_workouts as the source for task_id and makes clear this is for calendar removal rather than workout deletion. It does not explicitly name the alternative delete tool or spell out when-not to use this, but the boundary is strongly implied.

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