garmin-mcp

Overview Schema Source Related Servers Discussions Admin

garmin_workouts

Read-only

List saved Garmin workouts or retrieve one workout's readable steps, including duration, distance, targets, repeats, and strength exercises.

Instructions

Saved workouts: the list, or one workout's steps (duration or distance, targets, repeats, strength exercises).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`raw`	No	Garmin's workout JSON instead of the readable steps
`workout_id`	No	Omit to list saved workouts. A number, or a UUID for Garmin Coach workouts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful substance beyond that by enumerating what the step output contains (duration or distance, targets, repeats, strength exercises), which partially substitutes for the absent output schema.

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?

A single fragment, front-loaded with the resource and immediately followed by the two modes. There is no filler, no restatement of the tool name, and nothing an agent must read past to reach the operative information.

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?

For a two-parameter read with no output schema, the description adequately sketches the return shape, and the raw/readable distinction is covered by the schema. Minor gaps remain around empty results and the difference between a list entry's summary and a full step tree.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, including the 'omit to list' and 'UUID for Garmin Coach workouts' cases. The description reinforces the list-vs-detail semantics but adds no format or syntax detail the schema lacks; baseline 3 applies.

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 description names the resource (saved workouts) and the two retrieval modes: the full list, or one workout's step breakdown. That distinguishes it from write-side siblings like garmin_create_workout and garmin_upload_workouts, though it never names an alternative or contrasts with garmin_courses.

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 'the list, or one workout's steps' phrasing implies the selection logic (omit the id to list, pass an id for detail), but usage is left implicit and the schema's parameter descriptions must carry it. No explicit when-to-use or when-not guidance is given.

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