Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_timetable

Read-onlyIdempotent

Fetch a teacher, student, class, or classroom timetable for a specific date or date range, returning lessons by day. Use target IDs from the roster for accurate results.

Instructions

Get the timetable for a teacher, student, class or classroom on a date (or a date range, see end_date). Read-only.

Args: target_type: 'teacher' | 'student' | 'class' | 'classroom'. target_id: person/class/classroom id as returned by get_roster. date_str: Single day, YYYY-MM-DD (default today). Ignored when end_date is given. end_date: When set, returns the timetable for every day from date_str (default today) to end_date inclusive, keyed by date — the equivalent of the former get_timetable_range. subdomain: School to query (defaults to the active subdomain).

Returns: Single-day shape: {'target', 'date', 'subdomain', 'lessons'}. Range shape: {'subdomain', 'range': {: single-day result}}. Days with no published data get an empty lessons list.

Notes: - For the logged-in user's own timetable prefer get_my_timetable; for a student by name/id use get_student_timetable. - Any school's whole-week plan for yourself: get_next_week_timetable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_strNo
end_dateNo
subdomainNo
target_idYes
target_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / end_date / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / end_date / type
      Removed value: -"string"
    • addedInput schema / properties / subdomain / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / subdomain / type
      Removed value: -"string"
  2. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / end_date
      Added value: +{
+  "default": null,
+  "title": "End Date",
+  "type": "string"
+}
  3. First observedv0.4.6

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses default behaviors (date_str defaults to today, subdomain defaults to active), precedence rules (date_str ignored when end_date is set), range semantics, and edge-case handling (days with no data return an empty lessons list). It also maps the tool to the former get_timetable_range.

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 with the core purpose, then organized into Args/Returns/Notes sections with no wasted sentences. It is longer than strictly minimal (the Returns block restates shapes the caller could infer), but every part is informative and scannable.

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 compensates by documenting both return shapes and the empty-day case, and it covers all five parameters, defaults, and sibling routing. An agent has everything needed to call and interpret 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 carries the full burden and does: it enumerates target_type's allowed values, states target_id's provenance (as returned by get_roster), documents date_str's format/default and its precedence against end_date, explains end_date's inclusive range keying, and notes subdomain's default.

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 (Get) and resource (timetable) plus the exact target scope (teacher, student, class, classroom) and temporal scope (date or range). It is immediately distinguishable from siblings like get_my_timetable and get_student_timetable, which it names.

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 routes the agent: prefer get_my_timetable for the logged-in user, get_student_timetable for a student by name/id, and get_next_week_timetable for a whole-week plan. Conditions and alternatives are stated, not implied.

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