Related Servers

With 148 tools spanning the same health/activity domains, boundaries blur: get_stats, get_user_summary, and get_stats_and_body all return daily summaries; get_activity_splits, get_activity_typed_splits, and get_activity_split_summaries have vaguely differentiated purposes; get_training_plan_workouts is explicitly a duplicate alias for get_garmin_coach_workouts. Some full-vs-summary pairs are well-noteed, but many near-duplicates force an agent to parse fine print to select correctly.

The overwhhelming majority follow a consistent snake_case verb_noun pattern (get_, set_, add_, delete_, create_, schedule_, upload_, download_). Minor deviations stand out: get_activities_fordate (missing underscore), get_userprofile_settings (missing underscore), get_weigh_ins vs add_weigh_in (pluralization inconsistency), and abbreviation mismatches like get_rhr_day vs get_heart_rates.

148 tools is extreme by any measure and far beyond what a coherent surface needs. Much of the bloat comes from redundant singular/plural pairs, summary/full variants that could be parameterized, four specialty create_*_workout builders alongside generic upload_workout, and an explicit legacy alias tool.

Coverage across the Garmin Connect domain is genuinely extensive: activities, workouts (upload/list/schedule/delete/download), courses, nutrition (food CRUD + logging), gear, devices, health metrics, and training analytics all have solid read and mostly write access. Notable gaps are deleting activities and goals/challenges/badges being strictly read-only, but these are workaroundable and the surface rarely dead-ends.