Skip to main content
Glama

unschedule_workout

Destructive

Remove a scheduled workout from the Garmin Connect calendar using its calendar-entry ID, while keeping the workout template in your library for later rescheduling.

Instructions

Remove a scheduled workout from the Garmin Connect calendar

    Deletes a calendar entry without deleting the underlying workout
    template — the workout stays in your library and can be re-scheduled.

    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.

    Note: the scheduled-workouts listing is an eventually-consistent index.
    If you just scheduled this workout, allow a moment before unscheduling
    so the id is available.

    Args:
        scheduled_workout_id: Calendar-entry id from get_scheduled_workouts
    

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

Input Schema

NameRequiredDescriptionDefault
scheduled_workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description goes further by specifying exactly what is and is not destroyed (calendar entry gone, workout template retained and re-schedulable). The eventual-consistency note explains a real failure mode not visible in annotations, though it says nothing about behavior when the id is stale or already removed.

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 action, then the disambiguation, then the critical id warning, then the caveat — a sensible priority order. The docstring-style 'Args:' block restates what the prose already established, which is mild redundancy but not harmful.

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?

For a one-parameter destructive tool with no output schema and no enums, the definition supplies the action, the destructive scope, the correct id source, and the timing precondition. Nothing an agent needs to call it 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?

Schema coverage is 0% and the single parameter is an integer with no description, so the description must carry the meaning — and it does, explaining that scheduled_workout_id is a calendar-entry id distinct from a workout id and naming the exact field and tool to source it from.

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 (remove a scheduled workout from the Garmin Connect calendar) and immediately scopes it against the superficially similar delete_workout by noting the underlying template survives. An agent can distinguish it from generic deletion tools without opening a 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?

Explicitly routes the agent to get_scheduled_workouts for the id and explicitly rules out get_workouts as an id source, plus a timing precondition for freshly scheduled entries. It does not address the plural unschedule_workouts sibling, but per the guidance no alternative is assumed from a name alone.

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