No user-submitted related servers found.
Scored across 12 tools
Several tool pairs have genuinely unclear boundaries: hyrox_pace and hyrox_splits both take a standalone 5 km time and produce run splits, volume_audit and get_muscle_volume both report hard sets per muscle group against weekly landmarks, and strength_benchmark and plates_zone2 both derive e1RM from a reference set. The stateless-vs-stateful distinction in the descriptions hints at the difference, but an agent would frequently have to guess which of a pair to call.
Names are all snake_case and readable, which is good, but conventions are mixed: get_sessions, get_profile, log_workout, plan_workout follow verb_noun while hyrox_pace, volume_audit, strength_benchmark, interference_tax, plates_zone2 are noun/noun_noun with no verb. The hyrox_* prefix is a useful grouping but the hyrox_autopsy vs hyrox_splits vs hyrox_pace distinction isn't encoded in the names.
12 tools sits comfortably in the well-scoped 3-15 range for a hybrid-athlete training assistant, and each nominal capability (log, plan, fetch, analyze) has a plausible home. The count is slightly inflated by the redundant overlapping pairs noted above, but nothing feels gratuitous at the surface level.
The core loop is covered — read profile/sessions, log completed work, plan future work, audit volume, benchmark strength, and analyze Hyrox performance — but there is no update or delete for logged/planned workouts, and get_profile has no corresponding profile/goal update tool. These are notable lifecycle gaps that will force agents into dead ends when a user mislogs or wants to change their race targets.