No user-submitted related servers found.
Scored across 14 tools
Most tools target clearly distinct slices of data (courses, grades, announcements, materials, teachers), and descriptions carefully explain the 'what do I still have to do' vs 'what's due soon' vs 'what's overdue' split. The tightest overlap is get_submission_status vs get_assignment_details, since the latter also reports the student's status, and get_whats_new aggregates several other tools' outputs — an agent may hesitate between the specific and the aggregate.
Every tool is snake_case with a predictable verb_noun shape (get_my_courses, get_todo, get_missing_assignments, get_course_teachers), and the single non-get verb (export_due_dates_calendar) describes a genuinely different action. Scope qualifiers like get_my_* vs get_course_* are used consistently.
14 tools sits in the sweet spot and each one maps to a distinct student question (what am I in, what's due, what's late, what did I get, what's new, who teaches me). The aggregate tools (get_whats_new, export_due_dates_calendar) earn their place as conveniences rather than duplicating surface for its own sake.
Read-only student workflows are well covered end-to-end: discovery of courses, per-class and cross-class assignment views, submission detail, grades, target-grade math, materials, announcements, and teacher contact. Gaps are minor but real — no way to fetch attachment/drive file contents, no archived-course access, and no write/submit operations if the server is intended to grow beyond read-only.