garmin-athletics-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_healthA | Fetch sleep, heart rate, Body Battery, stress, steps, calories and related data for a day. |
| get_recovery_snapshotC | Fetch daily recovery and available performance context. Not medical advice. |
| get_performance_metricsC | Fetch available VO2 max, recovery, race-prediction and training-status metrics. |
| list_workoutsA | List read-only normalized workout summaries in a bounded date range. |
| get_workout_detailsA | Fetch workout splits and details without downloading GPS route data. |
| compare_latest_workoutC | Compare the latest workout with median values from similar workouts. |
| get_athletics_trendsC | Summarize training volume, pace, wellness coverage, and available VO2 max history. |
| get_recent_athletics_trendsC | Convenience trend summary for the last 7 to 366 days. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Some tools have overlapping focus: get_recovery_snapshot and get_performance_metrics both include recovery data, while get_athletics_trends and get_recent_athletics_trends are similar except for time range. However, most tools have clearly distinct targets (daily health vs workouts vs trends).
Most tools follow a consistent 'get_' or 'list_' verb+noun pattern, with 'compare_latest_workout' as a minor deviation. The naming is readable and predictable overall.
Eight tools is well-scoped for an athletics data server, covering health, recovery, performance, workouts, and trends without bloat or sparseness.
The toolset covers the core read-only analytics domain well: daily health, recovery, performance metrics, workout listings/details/comparison, and trends. It lacks advanced features like fitness age or training load, but the main workflows are supported.