No user-submitted related servers found.
Scored across 198 tools
Many tools target closely related Garmin data, and several are explicit aliases or near-duplicates, such as get_stats for get_user_summary and get_stress_data for get_all_day_stress. The activity, daily-stats, weight, workout/scheduling, and gear families contain multiple overlapping read methods, so tool selection remains error-prone despite detailed descriptions.
Most names use a predictable snake_case verb_noun pattern with get_/set_/create_/delete_/add_/remove_ prefixes. Deviations such as bare accessors (display_name, full_name, user_name, unit_system) and get_userprofile_settings vs get_user_settings are minor but noticeable.
198 tools is far beyond a coherent single-server surface and forces an agent to navigate enormous, partially redundant families. Even for a broad Garmin Connect domain, exposing nearly every low-level endpoint and alias as a separate tool is an extreme mismatch.
The surface covers an unusually wide range of Garmin Connect domains: activities, wellness metrics, body composition, gear, workouts, courses, calendar, badges, nutrition, menstrual health, training plans, and devices. Some lifecycle gaps remain, such as limited write support for profile/settings and power zones, but most core workflows are present.