No user-submitted related servers found.
Scored across 15 tools
Most tools have sharply distinct purposes, and the descriptions actively steer selection (e.g. get_recovery_summary is 'aggregates only', get_daily_metrics is 'one day', get_trend is 'one metric over time'). The main residual overlap is between get_recovery_summary, get_trend and get_vo2max_history, all of which can answer 'how is my X going?', and between the three load-related tools, though the boundaries are documented. The propose/apply/undo trio is clearly delineated by 'nothing is written' vs 'only after explicit yes' vs its counterpart.
Uniform snake_case verb_noun convention throughout: get_*, propose_*, apply_*, undo_*, sync_*, analyze_*. Verbs are meaningful and consistent with the action's semantics (propose vs apply vs undo clearly encode lifecycle stage).
15 tools sit at the top of the well-scoped range and each maps to a distinct stage of the coach loop: read data, sync, plan, apply, undo, plus the rule-set reference. No filler tools and no duplicated capability.
Strong end-to-end coverage of the training-coaching lifecycle: data ingest, analysis, planning, write-back and rollback. Minor gaps: no tool to inspect the existing Garmin calendar or list open proposals, even though propose_week's 'the calendar wins' logic depends on that data, and no explicit accessor for the athlete's zones/profile that targeting relies on.