Garmin MCP Lite

Overview Schema Source Related Servers Discussions Admin

garmin_schedule_running_workout

Create structured running workouts with warmup, intervals, and cooldown, then schedule them to your Garmin Connect calendar by date.

Instructions

Create a structured running workout and schedule it to Garmin Connect calendar.

Args: name: Workout name (e.g. 'W1D2-E有氧跑10K'). date: Schedule date in YYYY-MM-DD format. description: Description of the workout. steady_km: Distance in km for a simple steady run (e.g. 10.0). pace_min: Faster pace bound (e.g. '5:20'). pace_max: Slower pace bound (e.g. '5:35'). warmup_km: Warmup distance in km (optional). warmup_pace_min: Warmup faster pace bound (optional). warmup_pace_max: Warmup slower pace bound (optional). intervals: List of interval dicts, each with keys like: {'distance_km': 6.0, 'pace_min': '4:25', 'pace_max': '4:30', 'description': 'Tempo'} or {'duration_min': 30.0, ...}. cooldown_km: Cooldown distance in km (optional). cooldown_pace_min: Cooldown faster pace bound (optional). cooldown_pace_max: Cooldown slower pace bound (optional).

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": {
      "name": "<name>",
      "date": "<date>"
    },
    "name": "garmin_schedule_running_workout"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`name`	Yes
`pace_max`	No
`pace_min`	No
`intervals`	No
`steady_km`	No
`warmup_km`	No
`cooldown_km`	No
`description`	No
`warmup_pace_max`	No
`warmup_pace_min`	No
`cooldown_pace_max`	No
`cooldown_pace_min`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.10Nov 9, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and falls short: it never says this writes to the external Garmin Connect account, whether auth tokens are required, whether repeated calls create duplicates, or whether the scheduled workout can be undone. It documents argument shapes well but discloses nothing about side effects or failure modes for a mutation tool.

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?

The purpose sentence is front-loaded and the Args list is scannable, with examples that earn their space. It is long, but that length is driven by 13 undocumented parameters rather than padding; a couple of lines (warmup/cooldown pace min/max) could be compressed into grouped notes.

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

Completeness3/5

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

The output schema exists, so return values need not be described, and all parameters are at least named. Still, for a 13-parameter mutation tool with zero annotations, missing guidance on combining steady_km with intervals, on which pace fields are required in practice, and on side effects leaves real gaps an agent could stumble into.

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% across 13 parameters, so the description must compensate — and it largely does, giving every parameter a name, a type hint, a format example ('5:20', '10.0'), and marking the optional ones. The interval dict keys are illustrated with two concrete example objects, including the distance_km vs duration_min alternative. It loses a point for not clarifying the interaction between steady_km and intervals or the dependency of pace_min/pace_max on the distance parameters.

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 first line states a specific verb and resource: 'Create a structured running workout and schedule it to Garmin Connect calendar.' That is far more informative than the name alone and implies a write to an external calendar. It does not, however, distinguish itself from the sibling garmin_schedule_cycling_workout or explain why a running-specific tool exists.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this versus garmin_schedule_cycling_workout, garmin_add_event, or garmin_training_plan, and no prerequisites (authentication, device sync, duplicate handling). The only usage hint is implicit — steady_km is described as being for 'a simple steady run' — but the description never says whether steady_km and intervals are mutually exclusive or can be combined.

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