Skip to main content
Glama

schedule_workouts

Add one or more workouts to specific dates on your Garmin Connect calendar in a single call, using existing workout IDs or inline workout data uploaded and scheduled together.

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; pace targets are in m/s, not
              min/km (5:00/km = 3.333 m/s).

    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"}]
    

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": {
      "schedules": "<schedules>"
    },
    "name": "schedule_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
schedulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing that inline workout_data causes a new workout to be uploaded before scheduling — an extra side effect the annotations alone would not reveal.

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 and mode distinction are front-loaded, followed by parameter notes and two compact examples that each earn their place. The docstring 'Args' formatting is slightly mechanical but not padded.

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?

For a batch write with no output schema, the description omits what comes back and, more importantly, how partial failures behave (e.g., one bad calendar_date among several items) — a material gap for an all-or-nothing assumption. It also defers the full workout_data shape to upload_workout, which is a reasonable but incomplete handoff.

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?

Schema description coverage is 0% and the schema is an untyped array of objects, so the description carries the whole burden — it documents calendar_date (YYYY-MM-DD), workout_id, workout_data, the conditional requirement between the last two, and the non-obvious pace-unit rule (m/s, with a worked 5:00/km example). It also shows concrete nested payload examples.

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 opening line gives a specific verb and resource ('Schedule multiple workouts to specific calendar dates') and the phrase 'in a single call' signals the batch scope that separates it from the singular schedule_workout sibling. It stops short of naming an alternative, but the plural/batch framing is unambiguous.

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?

It clearly explains the two invocation modes (reference an existing workout_id versus supply inline workout_data that is uploaded then scheduled) and cross-references upload_workout for the data structure. However, it never states when an agent should prefer schedule_workout or schedule_week over this batch tool, so alternative selection is left to inference.

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

Deploy Server

Other Tools