Fetch upcoming exams and tests within a set number of days ahead. Use it to plan study schedules by retrieving a student's future WebUntis test dates.
Fetch upcoming exams and tests.
Args: days_ahead: Number of days to look ahead (default: 30)
| Name | Required | Description | Default |
|---|---|---|---|
| days_ahead | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Fetch' reasonably implies a read-only retrieval and 'upcoming' adds a time-scoping constraint, but it does not explicitly state read-only safety, permissions, rate limits, or side effects.
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?
Very short and front-loaded: the purpose is stated in one sentence, followed by a compact Args section. Every element earns its place with no filler.
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?
An output schema exists, so return values do not need explanation. The description covers the tool's purpose and its one parameter; the main gap is missing usage guidance relative to siblings, but for a simple read tool this is mostly complete.
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?
The single parameter has 0% schema description coverage, so the description must compensate. It explains that days_ahead is the number of days to look ahead and restates the default of 30, which gives adequate semantic meaning for invocation.
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?
States a specific verb and resource: 'Fetch upcoming exams and tests.' This clearly distinguishes the content from siblings like get_homework, get_absences, or get_timetable, but it does not explicitly differentiate itself from those alternatives by naming when each should be used.
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?
Provides no explicit guidance on when to use this tool versus siblings such as get_timetable, get_today, or get_tomorrow. The days_ahead default is mentioned, but there are no inclusion or exclusion criteria, prerequisites, or alternative-routing hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.