Skip to main content
Glama

mywhoosh_update_workout

Replace an existing custom workout in place using its ID to fix typos or change targets while keeping calendar links intact. Re-schedule calendar entries if their name or TSS must change.

Instructions

Replace an existing custom workout in place (same id), e.g. to fix a typo or change targets.

Same arguments as mywhoosh_create_workout plus workout_id; the whole workout is replaced. The id stays, so calendar entries keep pointing at it. Calendar entries keep their own copy of name and TSS, which is not updated: re-schedule if those must change.

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": "<name>",
      "blocks": "<blocks>"
    },
    "name": "mywhoosh_update_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
blocksYes
erg_modeNo
ftp_wattsNo
workout_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral load and does it well: it discloses that the entire workout is replaced rather than patched, that the id is preserved, and the non-obvious side effect that calendar entries hold their own stale copies of name and TSS. It omits irreversibility, required permissions, and behavior when workout_id does not exist.

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?

The purpose and the create-vs-update relationship are front-loaded in the first two sentences, and the caveat about calendar copies follows logically. There is mild redundancy between "The id stays, so calendar entries keep pointing at it" and the following sentence about calendar copies.

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 six-parameter mutation with a deeply documented nested Block schema and no output schema, the description covers the essential semantics: in-place replacement, identity retention, and the calendar side effect that would otherwise surprise an agent. It leaves the less critical top-level fields (erg_mode, ftp_watts, description) unexplained.

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 reported as 0% at the top level, so the description must compensate; it adds real value by explaining that blocks is a full replacement payload and that workout_id is the preserved identity. However, it explains nothing about name, description, erg_mode, or ftp_watts, and defers the rest to a sibling tool's schema rather than documenting them here.

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?

States a specific verb and resource ("Replace an existing custom workout in place") and immediately disambiguates from the sibling by naming mywhoosh_create_workout and describing the delta ("plus workout_id"). An agent can tell update apart from create without opening either schema.

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?

Gives concrete when-to-use triggers ("to fix a typo or change targets") and implicitly routes creation to mywhoosh_create_workout and calendar refresh to re-scheduling. It stops short of an explicit "do not use this to create a new workout" exclusion or an error-condition statement, so it is strong but not fully exhaustive.

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