Retrieve all school class names for the current school year, providing identifiers to fetch any class's timetable.
List all classes at the school for the current school year.
Returns class names that can be used with the get_class_timetable tool to fetch any class's schedule.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| 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 burden. It does disclose the scope (current school year) and that it returns class names, but says nothing about permissions, pagination, or whether results are exhaustive/cached for a zero-parameter read.
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?
Two short sentences with the purpose front-loaded and the downstream chaining detail second. No filler and no redundancy with the schema.
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 the description needn't document return values, and it correctly stays out of that. For a simple zero-param read tool it is essentially complete, with only minor gaps around freshness and ordering left unstated.
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 tool takes zero parameters, so the baseline is 4. The description adds nothing parameter-related because there is nothing to disambiguate, and the schema fully covers the empty argument object.
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 ('List all classes'), adds a scope ('current school year'), and clarifies that the output is class names. It points at the downstream sibling get_class_timetable, so an agent can place it in the workflow, though it doesn't contrast itself against the other list-like siblings.
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?
The second sentence gives a clear use context: the returned class names feed get_class_timetable to fetch a schedule. That is an actionable usage hint, but there are no explicit when-not-to-use conditions or alternatives to this call itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.