MCP server exposing Garmin Connect endpoints as tools for health, activity, workout, coaching, training plan, and performance data
30 tools with consistent verb-noun naming and structured schemas. Most tools have descriptions (10-150 chars, below baseline 194), but many lack depth on WHEN to use them or prerequisites. Input schemas present for all tools with proper types, but parameter descriptions are minimal (often 1-2 lines). Output schemas are not documented in the tool definitions themselves, agents must infer structure from descriptions. Error handling is mentioned in SERVER_INSTRUCTIONS but not per-tool. Security is good (no secrets in params), but tool composition could be tighter (e.g., activity mutations scattered across files).
Apply a training plan
Create a new workout
Delete an activity
Delete a workout
Download an activity file
Get a single activity by ID with optional detail and laps
Get lap-by-lap data for an activity
Output schemas not documented in tool definitions. Agents must infer response structure from descriptions alone, risking misinterpretation of nested fields, pagination, and error envelopes.
Parameter descriptions are minimal (1-2 lines). Missing guidance on format constraints (e.g., date format YYYY-MM-DD is stated but not validated), valid ranges, and dependencies between parameters.
Destructive tools (delete_activity, delete_workout) lack confirmation or dry-run support. No per-tool error guidance; agents rely on generic SERVER_INSTRUCTIONS for recovery hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2025-06-18+ | v2 |
Get metric stream data for an activity
Get weather data for an activity
Get heart rate time-in-zone breakdown for an activity
Get a bounded recovery, load, execution, and plan snapshot for coaching
Get daily body battery energy level data
Get daily heart rate statistics
Get daily sleep data
Get daily step count data
Get daily stress level data
Get performance metrics and statistics
Get the current training plan
Get current training status
Get VO2 max estimates
Get a single workout by ID
List recent activities with optional filtering
List available workouts
Check authentication status of the saved Garmin session
Non-raising configuration, session, and MCP diagnostics
Rename an activity
Change the activity type
Complete a Garmin login awaiting multi-factor authentication
Update an existing workout
Upload an activity file
Tool composition scattered across multiple files (activities.py, activities_write.py, workouts.py, etc.) without clear separation of concerns. Some tools do multiple things (e.g., get_activity with optional detail and laps).
create_workout and update_workout accept generic 'workout_data' object without schema. LLMs cannot infer required fields, nested structure, or valid values for workout definition.