Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_timetable_changes

Read-onlyIdempotent

Fetch substitution and timetable changes for a school date, defaulting to today. Use it to check schedule updates and pair with missing teacher data.

Instructions

Get substitution/timetable changes for a date (default today). Read-only.

Args: date_str: YYYY-MM-DD (default today). subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'date', 'subdomain', 'changes': [serialized substitutions]}. Empty list when nothing changed or the school publishes none.

Notes: - Pair with get_missing_teachers for the full substitution picture. - For one student's plan on a day use get_student_timetable / get_timetable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strNo
subdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • addedInput schema / properties / date_str / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / date_str / type
      Removed value: -"string"
    • 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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the leading 'Read-only.' mostly restates structured data. The description does add real behavior beyond annotations: the today/active-subdomain defaults and the fact that an empty list is the normal no-change signal, which prevents the agent from misreading an empty response as an error.

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-loaded one-line summary followed by clean Args/Returns/Notes sections, with no wasted sentences. Minor redundancy between the summary's 'Read-only' and the annotations, but every block earns its place.

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 ({'date','subdomain','changes': [...]}) and the empty-list case, plus the sibling routing an agent needs. Nothing required to call or interpret this tool correctly is missing.

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 carries the full burden and does so: date_str is documented as YYYY-MM-DD with a today default, and subdomain as the school to query defaulting to the active subdomain. Both of the two params gain format and default semantics absent from the schema.

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 first sentence names a specific verb ('Get') and resource ('substitution/timetable changes') plus the scope ('for a date, default today'), and the Notes distinguish it from get_student_timetable / get_timetable. An agent can tell it apart from the other timetable siblings 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?

Notes explicitly route the agent: pair with `get_missing_teachers` for the full picture, and use `get_student_timetable` / `get_timetable` for a single student's plan. Both the alternative and the condition that selects it are stated, leaving nothing to inference.

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