Skip to main content
Glama

reschedule_workout

DestructiveIdempotent

Move a scheduled workout to a new date on the Garmin Connect calendar, updating the existing calendar entry in place without creating duplicates.

Instructions

Move a scheduled workout to another date on the Garmin Connect calendar

    Moves the existing calendar entry in place, so its id stays the same
    and no duplicate entry is created. Prefer this over unschedule +
    schedule. Safe to repeat: moving an entry to the date it is already
    on changes nothing.

    IMPORTANT: scheduled_workout_id is the calendar-entry id, which is
    different from the workout's id. Get it from get_scheduled_workouts
    (the "scheduled_workout_id" field), not from get_workouts.

    Args:
        scheduled_workout_id: Calendar-entry id from get_scheduled_workouts
        calendar_date: New date in YYYY-MM-DD format
    

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": {
      "scheduled_workout_id": "<scheduled_workout_id>",
      "calendar_date": "<calendar_date>"
    },
    "name": "reschedule_workout"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendar_dateYes
scheduled_workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=true; the description adds genuinely new behavioral facts — the entry id is preserved and no duplicate is created — which an agent could not infer from the annotations. It does not state that the old date assignment is removed or whether the move is reversible, which is the remaining gap given destructiveHint=true.

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?

Front-loaded with the core action, then the id warning in an emphasized block. The trailing Args block partially repeats the id-source sentence already stated above, a small redundancy, but the prose stays short and every other sentence adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Two required params, no output schema, and the mutation semantics are all covered: where the id comes from, the date format, in-place behavior, and repeat safety. Nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

With 0% schema description coverage the description carries the full burden and does: it names the date format (YYYY-MM-DD) and disambiguates scheduled_workout_id from the workout's own id, pointing at the exact source field. This is the highest-value parameter guidance possible for this tool.

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 with scope: 'Move a scheduled workout to another date on the Garmin Connect calendar.' Immediately clarifies it edits the existing entry in place, which separates it from the create/unschedule siblings without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Prefer this over unschedule + schedule,' and gives the prerequisite for obtaining the id (get_scheduled_workouts, not get_workouts). The idempotency note tells the agent retries are harmless, removing the need for defensive pre-checks.

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

Deploy Server

Other Tools