Edupage MCP Server

Overview Schema Source Related Servers Discussions Admin

get_next_week_timetable

Get the timetable for each day of the upcoming week (Monday to Friday). Specify a class name, student name, or school to retrieve the schedule; defaults to your own timetable.

Instructions

Get timetable for each day of the upcoming week (Mon-Fri).

Args: class_name: Class name (e.g. '6e', '4a'). If empty, uses logged-in user's timetable. student_name: Student name to look up their class timetable (searches all schools). school: School subdomain (only needed with multiple schools and no student_name).

Returns: JSON object keyed by date with lean timetable lessons

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
`school`	No
`class_name`	No
`student_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses read behavior and return format ('JSON object keyed by date with lean timetable lessons'), but does not mention prerequisites or error cases. Annotation contradiction false.

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 a one-line summary, followed by structured Args and Returns sections. Every sentence adds value, no redundancy.

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?

Given the existence of an output schema, the description adequately covers return structure. However, it omits edge cases (e.g., no timetable found) and does not specify lesson details. Overall sufficient for a read tool.

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?

Description explains all three parameters in detail (class_name with example, student_name scope, school necessity), adding significant meaning beyond schema's types and defaults. Schema coverage is effectively 100% via description.

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?

Description clearly states 'Get timetable for each day of the upcoming week (Mon-Fri)', specifying verb and scope. It distinguishes from sibling 'get_timetable' which likely handles other date ranges.

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

Usage Guidelines3/5

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

Provides clear parameter usage context (class_name, student_name, school) but lacks guidance on when to use this tool versus siblings like 'get_timetable' or 'get_timetable_changes'.

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