No user-submitted related servers found.
Scored across 91 tools
Some tool clusters overlap meaningfully, such as submission status (get/inspect/preview_inspect), calendar/timeline reads (list_calendar_events, list_upcoming_events, list_pending_work, get_work_item), and the generic preview_student_action/execute_student_action versus specific action tools. The detailed descriptions help, but with 91 tools an agent must read carefully to avoid misselection.
The vast majority of tools follow a clear snake_case verb_noun pattern, and the preview_/action pairing is highly consistent. Minor deviations like auth_status and generic names like execute_student_action and call_student_read break the strict pattern slightly, but the overall scheme remains predictable.
91 tools is an extreme count for a single MCP server. Many tools are paired preview/action variants, compatibility stubs, or blocked endpoints that could be consolidated, making the surface far larger than necessary and difficult to navigate.
The server covers a broad student-facing lifecycle end-to-end: courses, assignments, quizzes, forums, messaging, calendar, grades, completion, badges, notifications, and official USC timetables/exams. Even blocked tools have explicit alternative flows, so there are no major workflow dead-ends.