Fetch upcoming school events including trips, excursions, meetings, and holidays. Supply the EduPage subdomain to receive a list of scheduled events.
Get upcoming school events (trips, excursions, meetings, holidays...).
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No |
Changes observed during successful MCP inspections.
v0.4.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Get' implies read-only retrieval, but the description does not disclose return format, ordering, timezone handling, or how 'upcoming' is defined. Without an output schema, more behavioral detail is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one compact, front-loaded sentence with useful examples in parentheses and no filler. It is concise and scannable, though it sacrifices needed parameter and behavioral detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple getter the description gives a minimal starting point, but with no output schema, no annotations, and an undocumented optional parameter, it is not complete enough for an agent to confidently understand the result shape or whether subdomain affects the response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description never mentions the 'subdomain' parameter. The single parameter is left to be understood only from its title, and the description adds no meaning, allowed values, or optionality context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and a clear resource ('upcoming school events'), with concrete examples in parentheses. It distinguishes the tool's subject from siblings like get_news or get_meals, though it does not explicitly name a differentiating sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternative event- or schedule-related siblings, no exclusions, and no prerequisites. The agent must infer usage solely from the purpose phrase.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.