No user-submitted related servers found.
Scored across 138 tools
The set contains multiple overlapping clusters: get_activities/get_activities_by_date/get_activities_fordate, get_stats/get_user_summary/get_stats_and_body, several full-vs-summary metric pairs, and an explicit duplicate alias in get_training_plan_workouts vs get_garmin_coach_workouts. Detailed descriptions help, but agents will often have to guess which of several near-synonymous getters returns the data they need.
Most tools follow a get_* pattern, but consistency breaks down with names like get_activities_fordate, get_userprofile_settings, set_perceived_effort vs set_activity_feel, and get_weigh_ins vs add_weigh_in. The mix of get/add/set/create/upload/log/upsert verbs across related operations makes the naming convention unpredictable.
138 tools is an extreme count, well beyond the 50+ threshold for a low score. While Garmin's API surface is broad, this many tools could be consolidated into domain-focused tools with parameters instead of exposing one tool per endpoint variant.
The tool surface covers virtually all Garmin Connect domains: activities, health metrics, devices, workouts, nutrition, courses, challenges, body composition, and more, with CRUD coverage for most areas. Minor gaps exist such as no delete-activity tool and no course update, but core workflows do not hit dead ends.