Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_roster

Fetch students, teachers, classes, classrooms, or subjects from an EduPage school. Provide the roster type to return the matching list.

Instructions

Get a school roster: students, teachers, classes, classrooms or subjects. Read-only.

Args: roster_type: Which roster to return: - 'students' — students in the logged-in user's class (formerly get_students). - 'all_students' — a short list of all students in the school (formerly get_all_students). - 'teachers' — all teachers (formerly get_teachers). - 'classes' — all classes (formerly get_classes). - 'classrooms' — all classrooms (formerly get_classrooms). - 'subjects' — all subjects (formerly get_subjects). subdomain: School to query (defaults to the active subdomain).

Returns: dict keyed by the roster name, e.g. {'subdomain': ..., 'teachers': [...], ...}.

Notes: - For the students visible to the logged-in account (parents: their linked children; students: classmates) prefer get_my_students. - To look one student up by name use find_student. - Returned person/class ids feed get_timetable (target_type/target_id) and switch_to_student.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subdomainNo
roster_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the behavioral burden. It explicitly states the tool is read-only and describes the return shape as a dict keyed by roster name with an example, which goes beyond minimal disclosure. It does not cover auth or rate limits, but for a read-only roster lookup the provided transparency is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with clear Args, Returns, and Notes sections. Each sentence contributes either parameter semantics, return behavior, or routing to alternatives, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only two parameters, no output schema, and no annotations, this description is complete: it documents all parameter values, default behavior, return shape, read-only nature, and important relationships to sibling tools. An agent has everything needed to select and call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully compensate, and it does. Every roster_type option is explicitly listed with its meaning and former tool name, and subdomain is described as the school to query with a default to the active subdomain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description begins with a specific verb and resource, 'Get a school roster', and immediately enumerates the exact roster types: students, teachers, classes, classrooms or subjects. The inline values and formerly-named tool references make it easy to distinguish this from related roster tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The Notes section explicitly tells the agent when to prefer alternatives: use get_my_students for students visible to the logged-in account, and use find_student for a single student lookup. It also explains how returned IDs connect to get_timetable and switch_to_student, giving clear contextual routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools