Retrieve all departments in an organization, ordered by hierarchy, to view the organizational structure and navigate department levels.
List all departments in an organization, ordered by their hierarchy.
| Name | Required | Description | Default |
|---|---|---|---|
| organization | Yes | organization identification string |
| Name | Required | Description | Default |
|---|---|---|---|
| departments | Yes | ||
| organization | Yes |
Changes observed during successful MCP inspections.
v2.0.0Output schema / properties / departments / items / properties / department / descriptionRemoved value: -"name of the department"Output schema / properties / departments / items / properties / id / descriptionRemoved value: -"external unique department identifier (if set for the department)"Output schema / properties / departments / items / properties / leaders / descriptionRemoved value: -"leaders of the department"Output schema / properties / departments / items / properties / leaders / items / properties / name / descriptionRemoved value: -"name of the leader"Output schema / properties / departments / items / properties / leaders / items / properties / user / descriptionRemoved value: -"user identification string"Output schema / properties / departments / items / properties / level / descriptionRemoved value: -"depth of the department within the hierarchy (0 for root level departments)"Output schema / properties / departments / items / properties / members / descriptionRemoved value: -"number of (visible) members in the department"Output schema / properties / departments / items / properties / parent / descriptionRemoved value: -"name of the parent department (null for root level departments)"Output schema / properties / departments / items / properties / permission / descriptionRemoved value: -"permissions given to the members of the department"Output schema / properties / departments / items / properties / permission / properties / content / descriptionRemoved value: -"permission level to contents in organization"Output schema / properties / departments / items / properties / permission / properties / members / descriptionRemoved value: -"permission level to members in organization"Output schema / properties / departments / items / properties / permission / properties / organization / descriptionRemoved value: -"permission level to organization"Output schema / properties / organization / descriptionRemoved value: -"organization identification string"v1.2.17Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral detail beyond annotations by specifying the output ordering 'by their hierarchy'. No contradiction with annotations.
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?
A single, front-loaded sentence conveys the action, resource, scope, and ordering with zero filler. Every word contributes to understanding the tool's purpose.
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 one-parameter read-only tool with a full output schema and safety annotations, the description is complete. It tells the agent exactly what the tool returns and how it is ordered; no additional information is needed to invoke it correctly.
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 100%, so the single 'organization' parameter is fully documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides, matching the baseline of 3.
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?
Description states the specific verb 'List', the resource 'departments in an organization', and the ordering behavior 'by their hierarchy'. The plural 'departments' clearly distinguishes it from the sibling tool edubase_get_organization_department which targets a single department.
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 description makes the use case clear: retrieving all departments of an organization. It does not explicitly name alternatives or provide exclusion criteria, but the plural vs singular sibling tool names strongly imply when this tool should be used instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.