No user-submitted related servers found.
Scored across 28 tools
Most tools have clearly distinct resource+action targets, and the read/write boundary is well documented (e.g. prepare vs commit vs verify in the grading flow). A few clusters still overlap: get_submissions, get_submission_content and get_assignment_grading_overview all return submission/grade data at different granularities, and get_course_groups vs get_group_members both return member lists. provide_feedback also overlaps in outcome with the batch grading tools, though its description explicitly redirects bulk cases to prepare/commit.
Nearly all names follow a snake_case verb_noun pattern (get_courses, create_course_group, add_group_member, post_forum_discussion, download_moodle_file), which is predictable and readable. Minor deviations exist: «provide_feedback» uses a less standard verb than send_message/post_forum_discussion for what is effectively an update operation, and some get_* names are long compound phrases (get_assignment_grading_overview, get_moodle_capabilities) breaking the simple verb_noun shape.
At 28 tools the surface sits above the comfortable 3-15 band and feels heavy, with six group-management tools and seven grading/submission tools. The breadth is partly justified because the server spans genuinely separate domains (grading workflows, group management, files/OCR, forums, messaging), but a few read variants (get_submissions vs get_assignment_grading_overview vs get_submission_content) inflate the count more than necessary.
The core teaching lifecycle is well covered: discover courses/contents/students, read assignments/quizzes/submissions, grade individually or via a guarded batch flow, manage groups and members, post to forums, send messages, and fetch/read files with OCR. The main gaps are the absence of a delete/update group operation (create/add/remove exist but no remove_course_group) and no edit/delete for forum posts or messages, which could dead-end some management workflows.