garmin-connect-api

Unschedule workout

unschedule_workout

DestructiveIdempotent

Remove a scheduled workout from your Garmin calendar without deleting the saved workout. Use the calendar entry ID, not the workout ID, to cancel or move a planned session.

Instructions

Remove one entry from the Garmin calendar; the saved workout itself is kept.

Takes the schedule_id from list_scheduled_workouts, schedule_workout, or a create_* call made with schedule_date; not the workout_id. To move a workout, unschedule it and schedule_workout it on the new date. To delete the workout itself, use delete_workout.

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

Input Schema

Name	Required	Description	Default
`schedule_id`	Yes	The calendar entry's id, not the workout's.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so safety/idempotency are covered. The description adds genuinely useful context beyond them: only the calendar entry is removed while the saved workout persists. It stops short of noting reversibility or error behavior on a bad id, so not a 5.

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?

Short, front-loaded, and every clause earns its place: the core effect first, then the id-source guidance, then the two alternative-routing sentences. No filler.

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?

An output schema exists so return values need not be explained, and the single parameter is fully documented in the schema. Combined with annotations and the routing guidance, an agent has everything needed to call this correctly.

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 100%, so baseline is 3, but the description adds meaning: it names the valid sources of schedule_id and warns it is 'not the workout_id', directly addressing the most likely invocation error beyond the terse schema text.

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 one entry from the Garmin calendar') and immediately clarifies scope ('the saved workout itself is kept'). It distinguishes itself from delete_workout and schedule_workout, so an agent can select it without opening the schema.

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?

Names where the required id comes from (list_scheduled_workouts, schedule_workout, create_* with schedule_date), and explicitly routes the move case to unschedule+schedule_workout and the delete case to delete_workout. When-to-use and alternatives are both explicit.

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