No user-submitted related servers found.
Scored across 18 tools
Most tools have clearly distinct targets: search_courses_by_name vs list_courses, get_user vs search_users, and the four user_field_schema tools (get/refresh/update/reorder) are separable. Minor overlap exists where list_course_users and list_user_courses both span users and courses (opposite directions), and get_capabilities vs get_agent_runtime_config are both meta-tools that an agent could confuse.
All 18 tools use clean snake_case with a consistent verb_noun pattern (get_*, list_*, search_*, manage_*, refresh_*, update_*, reorder_*). The single deviation, search_courses_by_name, is still readable and follows the same convention family.
18 tools is slightly heavy for a read-oriented LMS client, with 4 tools devoted to user-field-schema administration and 2 to cache management. Each earns a place, but the schema-management cluster inflates the surface beyond the core browse/search workflow.
Course, user, and category discovery are well covered, but list_assignments explicitly delegates submissions to 'a separate tool' that does not exist, creating a dead end. Grade/submission retrieval and enrollment management are absent, leaving notable gaps for a full LMS surface.