Garmin MCP Server

by Taxuspt

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

schedule_workouts

Schedule multiple workouts on specific dates using existing workout IDs or inline workout data.

Instructions

Schedule multiple workouts to specific calendar dates

This adds workouts to your Garmin Connect calendar in a single call. Each item can either reference an existing workout by ID, or provide inline workout_data to upload-and-schedule in one step.

Args: schedules: List of workout schedules, each with: - calendar_date (str): Date to schedule the workout in YYYY-MM-DD format (required) - workout_id (int): ID of an existing workout to schedule (required unless workout_data is provided) - workout_data (dict): Inline workout JSON to upload first, then schedule (optional). When provided, workout_id is not required. Uses the same structure and target-value rules as upload_workout.

Examples: Schedule existing workouts by ID: [{"workout_id": 123456, "calendar_date": "2024-01-15"}, {"workout_id": 789012, "calendar_date": "2024-01-17"}]

Upload and schedule inline:
[{"calendar_date": "2024-01-15", "workout_data": {"workoutName": "Easy Run", ...}},
 {"workout_id": 789012, "calendar_date": "2024-01-17"}]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`schedules`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the high-level behavior (adds to calendar, supports inline upload), but it does not mention potential side effects like partial failures, duplicate handling, whether inline uploads create permanent workouts, or any permissions. This is decent but lacks depth.

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 well-structured with a summary, a compact Args section using bullet points, and clear examples. It is succinct without unnecessary jargon, and the key information is front-loaded.

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?

The description covers the core use cases, parameter constraints, and provides examples. However, it leaves some edge cases ambiguous, such as what happens if both workout_id and workout_data are provided in the same object, and it does not address error handling or return values (though output schema exists, which mitigates the latter). Overall it is fairly complete for basic usage.

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?

The input schema is minimal (just an array of objects with additionalProperties), but the description thoroughly explains each parameter: calendar_date required, workout_id required unless workout_data is provided, workout_data optional with structure and rules referencing upload_workout. The mutual exclusivity is clear and examples support the semantics.

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 clearly states the tool 'Schedule multiple workouts to specific calendar dates' and explains it adds workouts to the Garmin Connect calendar in a single call. It distinguishes itself from sibling tools like schedule_workout by explicitly being plural and batch-oriented, and it also clarifies two modes (reference existing or inline upload).

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 implies when to use this tool (for multiple workouts, single call) and provides examples, but it does not explicitly contrast with schedule_workout or state when not to use it. The alternative is only implied by the plural name and 'single call' wording, not directly named with a condition.

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

Deploy Server