No user-submitted related servers found.
Scored across 19 tools
Most tools target distinct resources or actions, but the course-related cluster (search_lectures, search_courses, get_course, get_course_details, get_course_dates) has overlapping-sounding names that require careful description reading. The descriptions explicitly separate token vs public endpoints, and get_course_dates' dual mode (courseId or lvNumber) is documented but still slightly ambiguous.
All tools follow a consistent snake_case verb_noun pattern (get_*, list_*, search_*). Scope prefixes like list_my_ vs. list_public_ and token vs. public naming reinforce meaning without breaking the convention.
19 tools are on the heavier side but justified by the broad student-information domain spanning identity, calendar, courses, grades, exams, fees, persons, semesters, and rooms. Some consolidation among the course lookup tools might be possible, but each tool has a clear role.
The surface provides solid read-only coverage of core student data: identity, calendar, own and public courses, dates, grades, exams, fees, persons, semesters, and rooms. Write operations such as exam registration and calendar creation are explicitly out of scope, and there are minor gaps like detailed exam or grade breakdowns, but agents can accomplish most informational workflows.