Related Servers

There is genuine conceptual overlap among the analysis tools (get_training_summary vs get_weekly_summary, get_training_load vs get_coach_context vs get_load_projection, and the get_wellness_data/get_recovery_snapshot/get_wellness_trends/get_nutrition_summary cluster), and the many activity tools (get_activities, get_activity_report, get_activity_details, get_activity_intervals, get_activity_streams) could be confused at a glance. However, the descriptions are unusually disciplined: they repeatedly state precedence ('Use first for any question about one activity') and name the sibling tool to use instead, so an agent can usually pick correctly. Boundaries are mostly clear, with a handful of overlapping summary/wellness tools as the weak spot.

Names follow a strict verb_noun snake_case convention throughout: get_*, list_*, compare_*, analyze_*, validate_*, preview_*, find_*. Verb choice is meaningful (get for single reads, list for enumerations, compare for cross-entity analysis) and no camelCase or ad-hoc styles appear.

52 tools is very heavy for the surface, and several clusters look consolidatable (weekly vs general training summary; four separate wellness/nutrition readers; multiple overlapping 'review' entry points). The domain is genuinely broad, but the count sits well past the point where an agent can hold the whole set in mind, which the server itself acknowledges by declaring get_activity_report and get_coach_context as 'use first' funnel tools.

The read/analysis surface is extremely thorough (activities, streams, intervals, wellness, nutrition, load, curves, plan, library), so most questions can be answered. But it is a dead-end for mutations: no create/update/delete tools are present, and descriptions reference missing tools (add_or_update_event, add_events_bulk, create_library_workout, update_sport_settings), so a user cannot actually write a workout or change thresholds despite the guidance promising it. That is a notable lifecycle gap rather than a full CRUD surface.