garmin-mcp

create_workout

Create a structured Garmin Connect workout from steps, durations, distances, and targets, then optionally schedule it for a date so it syncs to the user's watch.

Instructions

Create a structured workout in Garmin Connect, optionally scheduling it on a date.

    It syncs to the user's watch on the next sync. Requires GARMIN_ALLOW_WRITES=true.

Input Schema

Name	Required	Description	Default
`spec`	Yes	{name, sport: running\|cycling\|swimming\|walking\|hiking\|strength_training\|cardio_training\|hiit\|yoga\|pilates\|mobility\|other, description?, steps: [...]}. Each step is {type: warmup\|interval\|recovery\|rest\|cooldown\|other, one of duration_s \| distance_m \| lap_button: true, target?, note?} or {repeat: N, steps: [...]}. Targets: {type: hr_zone, zone}, {type: hr, bpm: [lo, hi]}, {type: power_zone, zone}, {type: power, watts: [lo, hi]}, {type: pace, min_per_km: ['4:50', '5:10']}, {type: speed, kmh: [lo, hi]}, {type: cadence, rpm: [lo, hi]}.
`schedule_on`	No	YYYY-MM-DD; defaults to today

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With annotations already indicating a non-read-only, non-destructive, open-world write, the description adds useful behavioral context: the workout syncs to the user's watch on the next sync and writes require GARMIN_ALLOW_WRITES=true. It does not cover failure modes or idempotency, but it meaningfully supplements the annotations.

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?

The description is two concise sentences, front-loading the purpose and then adding required behavior and permission context. There is no wasted text.

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 write tool with a complex nested schema, output schema, and annotations, the description is nearly complete: it covers purpose, optional scheduling, sync behavior, and required write permission. Slightly more guidance on when to prefer this over schedule_workout would make it fully complete.

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 100%, including a detailed nested spec object. The description only reiterates that scheduling is optional and does not add syntax or constraints beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Create a structured workout in Garmin Connect.' It also clarifies that scheduling is optional, which helps distinguish it from sibling tools like schedule_workout, though it does not name those siblings explicitly.

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

Usage Guidelines3/5

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

The description provides a key prerequisite ('Requires GARMIN_ALLOW_WRITES=true') but does not explain when to use this tool versus schedule_workout, update_activity, or other workout-related siblings. Usage is implied rather than explicitly guided.

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