Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_my_students

Read-onlyIdempotent

Retrieve the students linked to your EduPage account—parents see their children, students/teachers see classmates—to enable student switching and timetable access.

Instructions

Get the students visible to the logged-in account. Read-only: parent accounts see their linked children (parsed from the school homepage); student/teacher accounts see classmates. Uses cached data.

Args: subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'subdomain', 'students': [{person_id, name, class_id, ...}]} usable with switch_to_student and get_student_timetable.

Notes: - Prefer get_my_students over get_roster to see your children / classmates; get_roster(roster_type='all_students') lists the whole school. - Cache is refreshed by clear_student_cache; scan_students returns the same visibility across all schools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / subdomain / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / subdomain / type
      Removed value: -"string"
  2. First observedv0.4.6

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-obvious traits: results are served from cache, refreshed via clear_student_cache, and visibility varies by account type (school homepage parsing). It stops short of rate limits or pagination notes, but the caching and visibility disclosure is substantial.

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

Conciseness4/5

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

Front-loads the core purpose in the first sentence, then structures Args/Returns/Notes cleanly. The Returns block is justified because there is no output schema, though the section labels add some verbosity for a one-param tool.

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?

With no output schema, the description supplies the return shape ({'subdomain', 'students': [...]}) and names downstream tools (switch_to_student, get_student_timetable) that consume the person_id. Visibility rules, caching lifecycle, and alternatives are all present, leaving nothing essential missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the load for the single parameter. It documents 'subdomain: School to query' and its default ('defaults to the active subdomain'), which the schema's bare title/default does not explain. This is more than baseline for a 0%-coverage param.

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?

States a specific verb+resource ('Get the students visible to the logged-in account') and immediately scopes it by account type (parent vs student/teacher). It explicitly distinguishes itself from get_roster and scan_students, so an agent can route without opening any schema.

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?

Provides explicit when-to-use guidance: prefer get_my_students over get_roster to see *your* children/classmates, versus get_roster(roster_type='all_students') for the whole school. It also names the maintenance siblings (clear_student_cache, scan_students), covering the alternatives and their conditions.

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