EduPage MCP Server

get_next_week_timetable

Read-onlyIdempotent

Retrieve the logged-in user's Monday-Friday timetable for next week, grouped by weekday, with an optional school subdomain for read-only access.

Instructions

Get the Mon-Fri timetable for next week for the logged-in user, grouped by weekday. Read-only.

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

Returns: dict: {'monday', 'subdomain', 'week': [{weekday, date, lessons} x5]}.

Notes: - Weekdays are 'Po','Ut','St','Št','Pi'. - For the logged-in user on a single day use get_my_timetable; for any target (teacher/class/room/student) over a range use get_timetable with end_date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_next_week_timetable"
  }
}

Input Schema

Name	Required	Description	Default
`subdomain`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond them by disclosing the exact return shape and the weekday key convention ('Po','Ut','St','Št','Pi'), which is non-obvious domain behavior.

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?

Front-loaded with the core purpose in the first sentence, then clearly separated Args/Returns/Notes sections. No filler; each block earns its place.

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

Completeness4/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 dict structure, weekday format, and sibling routing, which is nearly everything an agent needs. Minor gaps remain (no error/permission behavior), but for a read-only single-param tool this is close to complete.

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 description coverage is 0%, so the description must carry the parameter meaning. It explains that `subdomain` is the school to query and, importantly, that it defaults to the active subdomain — a default behavior the bare schema (default: null) does not convey.

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 and resource with full scope: 'Get the Mon-Fri timetable for next week for the logged-in user, grouped by weekday.' It also implicitly distinguishes itself from the two timetable siblings that handle single-day and target/range queries.

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: use `get_my_timetable` for the logged-in user on a single day, and `get_timetable` with `end_date` for any target over a range. When-to-use and alternatives are fully spelled out.

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