No user-submitted related servers found.
Scored across 8 tools
Each tool has a clearly distinct purpose: search, get full course structure, grade progression, competency connections, course listing, cross-curricular matching, change tracking, and course history. Despite some conceptual overlap (e.g., get_competency_connections vs. search_cross_curricular), the descriptions clearly differentiate their focus (specific competencies vs. any element type).
All tool names follow a consistent snake_case verb_noun pattern: search_*, get_*, list_*. The verbs are meaningful (search, get, list) and the nouns clearly indicate the object (curriculum, course, grade, competency, etc.). No mixed conventions or ambiguous naming.
Eight tools is well-scoped for a curriculum data server. Each tool addresses a distinct query need (search, retrieval, progression, connections, listing, cross-curricular, changes, history) without redundancy or bloat. The count feels appropriate for the domain.
The tool surface covers the full range of expected queries for a curriculum server: discovery (list_courses), full-text search (search_curriculum), detailed course data (get_course_curriculum), progression analysis (get_grade_progression), interdisciplinary connections (get_competency_connections, search_cross_curricular), and change tracking (get_curriculum_changes, get_course_history). No obvious gaps for typical use cases; it's a comprehensive read-only API.