edupage
Related Servers
Alternatives to edupage
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables Claude to access ParentSquare school-parent communication platform, including feeds, calendar, conversations, and media files.488MIT
- FlicenseAqualityDmaintenanceEnables natural language queries about grades, GPA, attendance, and schedules by connecting Claude to StudentVue school dashboards. Includes analytical tools for grade simulation, what-if scenarios, and academic performance tracking based on live school data.19-
- AlicenseAqualityFmaintenanceEnables Claude to access the ParentSquare school-parent communication platform via its web interface and internal APIs, covering parent features like feeds, calendars, messages, forms, and payments, plus school admin roster management such as students, guardians, classes, and staff.481MIT
- AlicenseBqualityCmaintenanceEnables Claude to interact with Canvas LMS, allowing natural language queries about courses, deadlines, grades, and feedback.29MIT
- FlicenseNot gradedqualityDmaintenanceConnects Claude to Canvas LMS, enabling students to query their coursework, assignments, grades, deadlines, announcements, and calendar events through natural conversation instead of navigating the Canvas interface.8-
- AlicenseBqualityAmaintenanceEnables Claude to query your KRÉTA student data locally and read-only, including timetables, homework, grades, tests, and absences, using your own credentials via OAuth/PKCE.203Apache 2.0
TDQS
Scored across 26 tools
Most tools are resource-specific, but several retrieval tools overlap: get_timeline, get_notifications, and get_notification_history share nearly identical filters and return similar event-like objects, while get_homework is a subset of get_assignments. The descriptions are detailed enough to disambiguate with careful reading, but an agent could easily misselect between timeline and notification tools.
The get_<resource> pattern dominates and is applied uniformly across timetable, grades, students, teachers, classes, homework, meals, absences, and more. Non-get tools are clear, distinct actions (login, login_auto, rate_meal, send_message), with no mixed casing or inconsistent verb styles.
26 tools exceeds the reasonable ceiling and feels heavy for what is mostly one school-information API. Several overlapping query surfaces (timeline vs notifications vs notification_history; homework vs assignments) inflate the count and could be consolidated. A trimmed set of roughly 15-18 tools would be more appropriate.
The set covers most of Edupage's domains: timetable, timetable changes, grades, homework/assignments, absences, events, meals, news, messages, students/teachers/classes, subjects, periods, plus authentication and write actions. Minor gaps exist, such as no direct inbox message tool, no way to mark homework/notifications done, and no logout, but agents can answer most school-related queries without hitting dead ends.