Skip to main content
Glama

get_training_plan_workouts

Read-only

Retrieve Garmin Coach or training-plan workouts for the week containing a given date to view scheduled sessions and rest days.

Instructions

Compatibility alias for get_garmin_coach_workouts

    Prefer get_garmin_coach_workouts for new requests. This legacy tool
    returns the same Garmin Coach/training-plan data; do not call both for
    one request. 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.

    Adaptive training plans typically expose workout_uuid; other plan
    families may expose numeric workout_id. Pass whichever identifier is
    present to get_workout_by_id. The returned count includes rest days.

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

Input Schema

NameRequiredDescriptionDefault
calendar_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description goes well beyond them: it discloses the limited generation window of adaptive plans, that future dates may return nothing despite an active plan, that the count includes rest days, and that identifiers differ by plan family (workout_uuid vs numeric workout_id) and must be passed to get_workout_by_id. That is exactly the operational context an agent needs to interpret results.

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?

Front-loaded with the compatibility/preference statement, then edge cases, then identifier handling; every sentence carries information. The trailing 'Args:' block partially restates what the schema already declares and is the one mildly redundant element.

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, this covers identity, deprecation routing, result semantics (rest days counted, empty future windows), and downstream identifier usage, leaving no significant gap an agent would need to guess at.

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 coverage is 0% (a bare string with no description), so the description must carry the parameter, and it does: it specifies YYYY-MM-DD format and that the date is a reference date returning the week's workouts. It stops short of clarifying timezone or boundary behavior for week calculation, so it is strong but not exhaustive.

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 precisely that this is a compatibility alias for get_garmin_coach_workouts returning the same Garmin Coach/training-plan data, which is a specific verb+resource plus an explicit relationship to a sibling. An agent can identify both what it does and which tool is preferred 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?

Explicitly says 'Prefer get_garmin_coach_workouts for new requests' and 'do not call both for one request', giving both the alternative and the exclusion. It also states when to expect empty results (future dates under adaptive plans), covering the main failure mode an agent would misread.

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