MCP server to access Garmin Connect data, compatible with Gemini and other MCP clients
24 tools with consistent naming (verb_noun pattern) and reasonable descriptions (avg ~120 chars). All tools are READ_ONLY with clear intent. However, parameter descriptions are minimal (often single-line), output schemas are not documented, and error handling guidance is absent. No tool annotations (readOnlyHint, etc.). Pagination support exists in some tools but inconsistently applied. Missing dependency hints and recovery guidance.
Get recent activities with pagination.
Get activities between specified dates with pagination support. Activities are ordered newest-first. Use page/page_size for large histories. When has_more is true, pass next_page as page to get the next batch.
Get activities for a specific date
Get detailed information about a specific activity.
Get gear used in a specific activity.
Get lap/split data for an activity.
Output schemas not documented. LLMs cannot infer what fields to expect from responses, forcing them to guess at downstream field names and risking broken tool chains.
Parameter descriptions are minimal (single line, often generic). E.g., 'Date in YYYY-MM-DD format' lacks context on what date is being queried (activity date? stats date? device date?). LLMs need WHEN to use each tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Get body composition data for a single date or date range.
Get information about the last used Garmin device.
Get settings for a specific device.
Get solar charging data for solar-equipped devices.
Get all registered Garmin devices. Returns a list of all Garmin devices linked to the account, including model, firmware version, and battery status.
Get all gear/equipment for a user.
Get default gear assignments for activity types.
Get statistics for a specific piece of gear.
Get heart rate data for a specific date.
Get the primary training device.
Get respiration rate data for a specific date.
Get resting heart rate for a specific date.
Get detailed sleep data for a specific date. Returns sleep stages, duration, scores, and quality metrics.
Get SpO2 (blood oxygen saturation) data for a specific date.
Get daily activity stats with curated essential metrics. Returns a summary of daily health and activity data including steps, calories, heart rate, stress, body battery, and sleep metrics.
Get step count data for a specific date.
Get detailed stress data for a specific date.
Get user summary data for a specific date.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All 24 tools are READ_ONLY but this is not declared in the schema, forcing LLMs to infer safety from names alone.
Inconsistent pagination. get_activities_by_date supports page/page_size with has_more flag; get_activities uses limit/start; others have no pagination. Agents cannot apply a uniform pagination strategy.
No error handling guidance. If a date is invalid, a device_id does not exist, or a user_profile_number is wrong, the tool will fail silently. Descriptions do not hint at recovery steps (e.g., 'Call get_devices() first to find a valid device_id').