No user-submitted related servers found.
Scored across 12 tools
The save/get/list pairs (track, roadmap, exercise, lesson) are cleanly separated by resource and direction, and authoring vs. learner-facing tools are clearly distinguished. The one weak boundary is next_step vs. progress, since progress explicitly also returns 'the next step' and both report state, which could cause an agent to pick the wrong one when asked 'what should I do now?'.
Seven tools follow a strict verb_noun snake_case pattern (save_track, get_roadmap, list_tracks, save_exercise, get_exercise, save_lesson, get_lesson) plus mark_lesson_read. The remaining three (check, progress, next_step) break the pattern with bare verbs/nouns, but they remain readable and domain-obvious rather than chaotic.
Twelve tools is well within a healthy range and splits naturally into track/roadmap setup, authoring (exercise, lesson), and learner interaction (get_exercise, check, get_lesson, mark_lesson_read) plus guidance state. Each tool maps to a distinct step in the course lifecycle, with only slight redundancy between next_step and progress.
The surface covers the full authoring-and-learning loop: install/list tracks, save/get roadmap, author/get/grade exercises, save/get/mark lessons, and track progress. Minor gaps exist — no delete or uninstall operations for exercises, lessons, or tracks, and no way to enumerate existing exercises or lessons (agents must rely on next_step/progress to discover them).