edupage-mcp

Get school info

get_school_info

Read-only

Retrieve key school facts including bell schedule, email, class assignments, and counts of teachers, classes, subjects, and rooms from an EduPage subdomain or student name.

Instructions

Facts about a school (by subdomain or a student's name): the bell schedule with each period's start and end, the school's email, each student's class with its class teachers and home classroom, and how many teachers, classes, subjects and rooms it has.

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_school_info"
  }
}

Input Schema

Name	Required	Description	Default
`school`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the read-only nature is covered. The description adds valuable behavioral context by specifying the input forms (subdomain or student's name) and the breadth of returned facts, going beyond what annotations convey.

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?

A single sentence that efficiently packs a list of facts, front-loading the core purpose. It is informative without redundancy, though slightly long due to the enumeration; still, every element 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?

The description covers the tool's scope and parameter usage, and an output schema exists to document return values. It lacks explicit mention of any limitations or prerequisites (e.g., whether student name requires a specific format), but overall it is sufficiently complete for an agent to call it correctly.

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?

The schema provides zero description for the 'school' parameter (0% coverage), so the description's mention of 'by subdomain or a student's name' is essential. It clarifies the parameter's meaning but leaves ambiguity about the exact format (e.g., whether it's a URL subdomain or a plain string), preventing a perfect score.

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 description states a specific verb and resource: 'Facts about a school' and enumerates the exact data returned (bell schedule, email, student class info, counts). It clearly distinguishes from sibling tools like get_timetable or get_grades, which are specialized, making this the aggregator for school-level facts.

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?

The description implies use for school-wide information but does not explicitly state when to prefer this tool over more specific siblings (e.g., 'use get_timetable for period details'). There is no exclusion or alternative guidance, so an agent must infer the appropriate context.

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

Deploy Server