Skip to main content
Glama

get_workout_by_id

Read-only

Retrieve detailed workout information by numeric ID or UUID, including segments, step structure, and optional raw Garmin data for scheduled or training-plan workouts.

Instructions

Get detailed information for a specific workout

    Returns workout details including segments and step structure.

    Accepts either:
    - Numeric workout ID (from get_workouts, get_scheduled_workouts, or
      training-plan families that expose workout_id)
    - Workout UUID (from adaptive Garmin Coach/training-plan workouts)

    Rest-day UUIDs can resolve to a minimal record without a workout name
    or segments.

    Pace target values are speeds in meters per second. target_value_low
    and target_value_high preserve Garmin's targetValueOne/targetValueTwo
    order; they are not sorted by magnitude.

    Args:
        workout_id: Workout ID (numeric) or UUID (for training plan workouts)
        raw: Return Garmin's full workout JSON (the DTO format upload_workout
            describes) instead of the simplified summary, which leaves fields out.
    

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": {
      "workout_id": "<workout_id>"
    },
    "name": "get_workout_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNo
workout_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as a non-destructive read, and the description adds real behavioral context beyond them: rest-day UUIDs may resolve to a minimal record lacking a name or segments, pace targets are speeds in m/s, and target_value_low/high preserve Garmin's original ordering rather than being sorted. The raw flag's effect (full Garmin DTO vs. simplified summary that omits fields) is also disclosed.

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?

Structure is good — purpose first, then return shape, then accepted identifier forms, then edge cases and caveats. The only waste is the duplication of the numeric-vs-UUID explanation, which appears both in the "Accepts either" bullets and again in the Args section.

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?

With no output schema, the description still explains what comes back (segments, step structure, simplified summary that leaves fields out) and covers the degenerate rest-day case. For a two-parameter read tool, an agent has everything needed to call it correctly and interpret the result.

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%, so the description must carry the burden, and it does: workout_id is documented as accepting a numeric ID or a UUID with distinct provenance, and raw is documented as selecting Garmin's full workout JSON (the DTO format upload_workout describes) over a lossy simplified summary. That is meaning well beyond the bare anyOf/boolean schema.

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 opens with a specific verb and resource ("Get detailed information for a specific workout") and immediately scopes the return ("workout details including segments and step structure"). The ID-source notes (get_workouts, get_scheduled_workouts, training-plan families) make clear this is the single-workout fetch, distinct from the list-style siblings.

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

Usage Guidelines4/5

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

It states precisely which identifiers are acceptable and where each kind comes from, so an agent knows when this call is applicable. It does not name an alternative for cases where the workout is unknown or where a different retrieval path (e.g., scheduled vs. owned workout) might be preferred, so it stops short of explicit when-not guidance.

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