Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

units

Read-only

Retrieve organizational units (stores, locations, departments) from the academy hierarchy. List active or archived units with search and pagination, or get details by ID.

Instructions

Look up organizational units (stores, locations, departments) in the academy hierarchy. Units are the lowest level of the organizational structure. Use this for units themselves. For higher-level groupings (regions, divisions, areas), use the aboves tool instead.

Sub-actions:

  • list: List all active units with optional filtering by search term, parent Above Unit, or Above Unit ID. Supports pagination.

  • get: Get details of a single unit by ID, including name, external ID, and organizational placement.

  • list_archived: List archived (inactive) units. Supports pagination.

Returns JSON: { data, _meta: { tool, action, returned, truncated? } }. When truncated is true, apply filters or pagination params to narrow results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe sub-action to perform: 'list' for active units, 'get' for a single unit by ID, 'list_archived' for inactive units
searchNoSearch by unit title (e.g. 'Chicago'). Comma-separate multiple terms (e.g. 'Chicago,Boston'). Used with list action.
search_aboveNoFilter units by their parent Above Unit title (e.g. 'Northeast Region'). Used with list action.
above_idNoFilter units by Above Unit ID (e.g. 42). Used with list action.
startNoStarting position for pagination (e.g. 0). Used with list and list_archived actions.
limitNoNumber of units to return per request. Default: 100, max: 100000. Used with list and list_archived actions.
unitIdNoUnit ID (e.g. '100') or external ID. Required for: get. Set external_id=true if passing an external ID instead of the internal numeric ID.
external_idNoWhen true, treats unitId as an external ID instead of the internal Schoox ID. Default: false. Used with get action.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true and destructiveHint=false, which the description reinforces by stating it's a lookup tool. Beyond annotations, the description discloses response format with JSON containing data and _meta, truncation behavior, and sub-action effects. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a main purpose sentence, sibling distinction, sub-action breakdown, and response format. It is clear and informative, though slightly verbose; every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, no output schema, and multiple sub-actions, the description covers all aspects: actions, filtering, pagination, response structure, and truncation handling. It also references the sibling tool for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for each parameter. The description adds practical usage details, such as comma-separated search, external_id flag for get action, and pagination defaults. This adds value beyond the schema's basic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up organizational units, the lowest level in the hierarchy, and explicitly distinguishes from the sibling tool 'aboves' for higher-level groupings. The verb 'look up' and resource 'units' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly contrasts with 'aboves' tool, explaining when to use this tool (for units) and when not (for regions/divisions/areas). It also details sub-actions with their use cases, providing clear usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/schoox/schoox-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server