No user-submitted related servers found.
Scored across 21 tools
Most tools target a clearly distinct resource (messages, courses, materials, assignments, grades, schedule, requests, notifications), and the descriptions explicitly steer between near-neighbors (elk_get_user_info vs elk_get_academic_data vs elk_get_section/profile). The fuzzy spots are the three summary tools (my_today / my_week / my_deadlines), which share item schema and overlap on deadlines, plus the catch-all elk_get_section that overlaps its sibling readers. Descriptions resolve these well, so an agent can still choose correctly.
Strong snake_case with source prefixes (lms_*, elk_*, hse_*, my_*) and predictable verbs (list/get/search/open/clear/reset). Minor deviations: the aggregators use a my_* prefix with no verb-noun shape, and hse_changes / hse_changes_reset are noun-style rather than verb-first. Still highly readable and predictable overall.
At 21 tools this sits at the heavy end for what is essentially a read-only student dashboard. Several tools earn their place, but the my_today / my_week / my_deadlines trio plus hse_changes / hse_changes_reset / hse_clear_cache add substantial surface area for what could be fewer, parameterized tools.
Read coverage is broad and thoughtful (courses, materials, assignments, grades, mail, schedule, requests, notifications, academic card, portfolio, thesis), with an open_page fallback for unknown pages. However the surface is strictly read-only: no submitting assignments, no sending or replying to mail, and request submission is explicitly unimplemented, so common student workflows dead-end. open_page cannot substitute for form submission.