Garmin MCP Lite
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 |
|---|---|
| garmin_activitiesA | List recent activities filtered by date range and type. Args: start_date: Start date in YYYY-MM-DD format. Defaults to 7 days ago. end_date: End date in YYYY-MM-DD format. Defaults to today. activity_type: Filter by sport type. One of: running, cycling, swimming, diving, all. limit: Maximum number of activities to return. |
| garmin_activity_detailA | Get detailed metrics for a single activity by ID. Args: activity_id: The Garmin activity ID. fields: Optional list of extra data sections to include. Supported values: "splits", "hrZones", "laps", "gps". Omit to return the basic summary only. |
| garmin_training_planB | Get the scheduled training workout for a specific date. Args: date: Date in YYYY-MM-DD format. Defaults to today. |
| garmin_training_statusA | Get current training status summary. Returns training status label, VO2Max, acute training load, load focus distribution (aerobic_low / aerobic_high / anaerobic), recovery time, training readiness score, and sleep score. |
| garmin_healthA | Get health metrics for a specific date. Args: metric: The health metric to retrieve. Options: - "sleep" : Sleep duration, stages (deep/REM/light), and quality score. - "hrv" : HRV status, weekly average, and last-night reading. - "stress" : Average and peak stress levels. - "body_battery" : Body battery charge/drain, peak, and current level. - "spo2" : Blood oxygen saturation (average, lowest, latest). - "respiration" : Respiration rate (average, min, max). - "intensity" : Weekly intensity minutes vs. goal (moderate + vigorous). - "steps" : Daily step count vs. goal, floors climbed, and resting HR. - "all" : All of the above combined (default). date: Date in YYYY-MM-DD format. Defaults to today. |
| garmin_gearB | Get the gear library (shoes, bikes, etc.) with real cumulative mileage for each item. |
| garmin_deviceB | Get connected device information including firmware version, update availability, primary tracker role, and registration date. |
| garmin_hr_trendB | Get resting heart rate historical trend data. Args: period: Time window. One of: "7d" (7 days), "30d" (30 days), "90d" (90 days). |
| garmin_weekly_statsA | Get aggregated training volume statistics for a given period. Args: period: Time period. One of: "week" (7 days), "month" (30 days), "year" (365 days). |
| garmin_coachB | List active Garmin Coach training plans. |
| garmin_eventsA | Get upcoming race events from the Garmin calendar, including target distance and goal finish time. |
| garmin_challengesA | Get in-progress challenges and badge completion status, including virtual challenges and monthly badges. |
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 12 tools
Each tool addresses a distinct aspect of Garmin data: activities, activity details, health metrics, training, device, gear, challenges, events. No overlap in purpose.
All tools follow the pattern 'garmin_<noun>' or 'garmin_<adjective_noun>' in snake_case, providing a clear and uniform naming convention.
12 tools cover the core Garmin data domains without being excessive. Each tool serves a clear need, making the set well-scoped.
The tool set covers essential data retrieval (activities, health, training, device, etc.) but lacks write operations (e.g., creating activities or workouts). For a 'Lite' server, this is a minor gap.