edookit-portal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDOOKIT_SCHOOL | Yes | The subdomain of your Edookit portal, e.g., 'zs-example' for https://zs-example.edookit.net |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| portal_dashboardA | Get the main dashboard — student name, pinned items, this week's attendance, and timetable highlights. |
| portal_inboxB | List inbox items (messages, events, assignments, etc.). Optionally filter by type. |
| portal_evaluationsB | Get grades and evaluations grouped by subject. |
| portal_assignmentsC | Get homework assignments (upcoming, today, recent, or archive). |
| portal_examsA | Get upcoming or past exams and written tests. |
| portal_materialsC | Get teaching/learning materials. Optionally filter by course ID. |
| portal_lesson_plansB | Get lesson plans / curriculum content for the student. |
| portal_timetableA | Get the student timetable. Views: current week, static (permanent), upcoming events, archive. |
| portal_attendanceB | Get attendance records and statistics. Views: excuse (retroactive), report (forward by day), report-lesson (forward by lesson), excused, stats, overview. |
| portal_excuse_absenceB | Submit a retroactive excuse for absences on specific dates. |
| portal_report_absenceB | Report a future (upcoming) absence by day or by lesson. |
| portal_messagesA | List inbox, sent, or archived messages. |
| portal_get_messageA | Get the full content of a single message by its ID. |
| portal_send_messageB | Compose and send a new message to a recipient. |
| portal_paymentsA | Get payment history and outstanding balances. |
| portal_discussionsA | Get upcoming or archived discussions (parent-teacher talks). |
| portal_coursesA | Get enrolled courses, class groups, or available course enrolments. |
| portal_portfoliosB | Get student portfolio work items. |
| portal_libraryB | Get borrowed and available library books. |
| portal_consentsA | Get consent forms (agreements) and their status. |
| portal_searchB | Search the portal for any content by keyword. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools map cleanly to distinct portal sections, but portal_inbox and portal_messages both expose message-like items and could cause selection confusion. The attendance views also overlap conceptually with the separate absence reporting/excuse tools, though descriptions make the read vs. submit distinction clear.
Tool names consistently use a portal_ prefix and snake_case, and most retrieval tools follow a portal_<resource> pattern. Minor deviations such as portal_get_message, portal_send_message, and portal_report_absence break the otherwise uniform noun pattern.
21 tools is on the heavy side, though each maps to a real feature area of a student portal. Some redundancy between inbox/messages and attendance/absence tools means the set could likely be consolidated without losing capability.
The toolkit covers the main read surfaces of a school portal: assignments, exams, timetable, attendance, payments, library, consents, and more. Missing write actions such as submitting consents or booking discussions are minor gap relative to the portal's apparent read-heavy purpose.