garmin-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Check the Garmin connection and return the logged-in account profile (display name, full name). |
| get_daily_healthA | Daily wellness metrics for a date. Pick one or more via |
| get_trainingA | Training metrics for a date. Pick via |
| get_fitnessA | Fitness/performance metrics. Pick via |
| get_weightA | Body weight & body composition (weight, BMI, body-fat %) over a date range. Set include_raw for the individual weigh-in entries too. Default range: the last ~4 weeks. |
| get_steps_history | Step totals over a date range. granularity 'daily' (Garmin caps the span at 28 days) or 'weekly'. Default: daily, last ~4 weeks. |
| get_activity | Data for a single activity by activityId. Pick via |
| list_activities | List activities. Without dates: the most recent ones (use limit=1 for the last activity). With startDate/endDate and/or type: activities in that range, optionally filtered by type (e.g. running, cycling, swimming). |
| get_devicesA | Garmin devices paired to the account (model, firmware, last sync). |
| get_user_profileA | User profile & settings: units, preferences, activity level, etc. |
| get_goals | Goals filtered by status (active, future, or past). |
| get_workouts | Saved workouts on the account. |
| get_scheduled_workouts | Scheduled workouts / calendar for a month (defaults to the current month). |
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 7 tools
Each tool targets a distinct aspect of Garmin data: account info, weight, profile, daily health, training metrics, fitness/performance, and devices. No overlapping purposes.
All tools use consistent snake_case verb_noun pattern (e.g., get_weight, get_user_profile), with 'whoami' as a minor but acceptable variation.
7 tools cover a broad health/fitness domain without being excessive. The count is well-scoped for the server's purpose.
Covers major data categories (profile, weight, daily health, training, fitness, devices). Minor gaps like detailed activity logs are absent, but overall surface is solid for a read-only server.