Retrieve a full list of teachers in your school. Returns a JSON array of teacher records, with optional school subdomain for multi-school setups.
Get all teachers in the school.
Args: school: School subdomain (only needed with multiple schools).
Returns: JSON array of lean teacher records
| Name | Required | Description | Default |
|---|---|---|---|
| school | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the burden. It mentions the return type as a JSON array of lean teacher records, indicating a read-only operation. However, no details on authorization, rate limits, or potential errors are given. It is adequate but not rich.
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 extremely concise with three lines: purpose, argument, and return. It is front-loaded and contains no fluff, making it easy for an agent to parse quickly.
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?
Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description is fairly complete. It covers the core functionality and parameter usage. Minor gaps like error handling are acceptable for such a straightforward tool.
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 parameter 'school' is explained with a note about when it is needed (only with multiple schools). Since the input schema has 0% description coverage, this description adds necessary meaning beyond the schema, clarifying the parameter's purpose.
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 clearly states it gets all teachers in the school, which is a specific verb and resource. It distinguishes well from sibling tools like get_students or get_classes by focusing on the teacher entity.
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?
No guidance on when to use this tool versus alternatives is provided. There is no mention of when not to use it, prerequisites, or how it differs from other teacher-related tools. The only usage hint is for the parameter school.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.