Skip to main content
Glama

get_garmin_coach_workouts

Read-only

Retrieve Garmin Coach training-plan workouts around a chosen date, including plan metadata, sport, duration, completion status, rest days, and race days.

Instructions

Get Garmin Coach workouts around the given date

    Returns workouts from the active Garmin Coach/training plan, including
    plan metadata, workout identifiers, dates, sport, duration, completion
    status, rest days, race days, and workout intent when Garmin provides
    them. Adaptive plans expose only Garmin's currently generated window,
    typically the current week; future dates may return no workouts even
    while a plan is active. The count includes rest-day entries.

    Garmin's standalone Daily Suggested Workouts are generated on compatible
    devices. As of July 31, 2026, no supported or known Garmin Connect
    web/API endpoint, including those exposed by this project's
    python-garminconnect dependency, returns the device's upcoming DSW
    schedule. This tool returns Garmin Coach/training-plan workouts and does
    not synthesize device-generated suggestions.

    This is the preferred tool for Garmin Coach requests. The legacy
    get_training_plan_workouts tool returns the same data; do not call both.

    Adaptive Coach plans typically expose workout_uuid; other plan families
    may expose numeric workout_id. Pass whichever identifier is present to
    get_workout_by_id. Rest-day UUIDs may return minimal detail without
    workout segments.

    Args:
        calendar_date: Reference date in YYYY-MM-DD format (returns week's workouts)
    

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": {
      "calendar_date": "<calendar_date>"
    },
    "name": "get_garmin_coach_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendar_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), yet the description adds substantial behavioral context: adaptive plans expose only the currently generated window, the count includes rest-day entries, and rest-day UUIDs may return minimal detail without segments. The only shortfall is that return shape and any pagination or size limits are not characterized beyond an enumeration of fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening and the tool-selection guidance are front-loaded and earn their place, but the Daily Suggested Workouts paragraph runs five lines to make a single scoping point and includes a dated aside and a dependency name that an agent does not need in order to call the tool. The identifier paragraph (workout_uuid vs workout_id) is useful but could be tightened.

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?

For a single-parameter read tool with no output schema, the description covers scope, return contents, plan-generation window limitations, identifier handling for the follow-up get_workout_by_id call, and an explicit exclusion. Nothing an agent needs in order to call it correctly or interpret an empty result is missing.

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 must carry the parameter, and it does: calendar_date is documented as YYYY-MM-DD and, critically, is disclosed to return the week's workouts rather than a single day's. That week-scoping detail is meaning the type 'string' alone cannot convey; only a stricter note on range bounds or timezone handling keeps this from a 5.

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?

States a specific verb and resource ('Get Garmin Coach workouts') and immediately enumerates what the response contains: plan metadata, workout identifiers, dates, sport, duration, completion status, rest days, race days, and intent. It also names the sibling it overlaps with (get_training_plan_workouts) and declares itself the preferred one, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('preferred tool for Garmin Coach requests'), an explicit when-not-to-call-both rule against get_training_plan_workouts, and a scope exclusion for device-generated Daily Suggested Workouts. It also sets expectations that future dates may legitimately return nothing while a plan is active, which prevents false-negative interpretation.

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