Zone Two

Overview Schema Source Related Servers Discussions Admin

Create a workout

garmin_create_workout

Create structured running workouts with intervals, repeats, and pacing details, then schedule them to appear on your Garmin watch for training day.

Instructions

Create a structured running workout on Garmin, optionally scheduling it.

Steps are plain objects, in order. Each needs a ``kind`` (warmup, run,
interval, recovery, rest, cooldown) and a ``length`` — a distance like
"800m", "5km" or a time like "10min", "90s". Optionally add ``pace``
("4:30" or a range "4:30-4:20", minutes per kilometre) or
``heart_rate_zone`` (1-5), and a ``note``.

Repeats nest: ``{"repeat": 6, "steps": [{"kind": "interval", "length":
"800m", "pace": "4:30-4:20"}, {"kind": "recovery", "length": "90s"}]}``.

Once scheduled it appears on the watch on that date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`steps`	Yes
`description`	No
`schedule_date`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Sep 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description substantially exceeds the minimal annotations by disclosing the execution model: ordered step objects, accepted kind/length/pace formats, heart-rate zones, repeat nesting, and the fact that scheduling makes the workout appear on the watch. This is meaningful behavioral context and is consistent with readOnlyHint=false.

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 opens with the core action and then uses compact, concrete examples to define the nested step structure. It is detailed but every sentence earns its place, and the examples are immediately interpretable.

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 no explanation, and the description covers all non-obvious invocation details: step kinds, length units, pace formats, heart-rate zones, repeats, and scheduling side effects. An agent can construct a valid call without additional clarification.

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 description coverage is 0%, so the description carries the burden for parameter meaning. It thoroughly explains steps (kind, length, pace, heart_rate_zone, note, repeat) and schedule_date via the watch behavior, but name and description are left to their schema titles rather than explicitly described.

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?

The description states a specific verb (Create), a resource (structured running workout on Garmin), and an optional behavior (scheduling). It clearly distinguishes this tool from siblings like list_workouts and delete_workout by describing what the workout contains.

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 primary use case is clear: create a structured running workout and optionally schedule it. However, the description never names alternatives such as garmin_schedule_workout or states when not to use this tool, so the distinction from scheduling an existing workout is only implied.

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