Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

aboves

Read-only

List or get organizational hierarchy levels above units, such as regions or divisions, with optional filtering and pagination.

Instructions

Look up organizational hierarchy levels above units — regions, divisions, areas, districts, or any custom grouping configured in the academy. Use this for org hierarchy above the unit level. For units themselves (stores, locations, departments), use the units tool instead.

Sub-actions:

  • list: List all Above Units with optional filtering by type or search term. Supports pagination.

  • get: Get details of a single Above Unit by ID, including name, type, external ID, and parent information.

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' to browse Above Units, 'get' to retrieve a single Above Unit by ID
type_idNoFilter Above Units by Type ID (e.g. 328339). Use the types tool to discover available type IDs. Used with list action.
searchNoSearch by Above Unit title (e.g. 'New York'). Partial match supported. Used with list action.
startNoStarting position for pagination (e.g. 0). Used with list action.
limitNoNumber of Above Units to return per request. Default: 100, max: 100000. Used with list action.
aboveIdNoAbove Unit ID (e.g. 1286994). Required for: get. Set external_id=true if passing an external ID instead of the internal numeric ID.
external_idNoWhen true, treats aboveId 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?

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds behavioral details such as the return JSON structure (with `_meta` fields), pagination behavior, and the 'truncated' flag. This fully informs the agent of the tool's behavior and responses.

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

Conciseness5/5

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

The description is concise and well-structured. It front-loads the core purpose, then presents sub-actions with their associated parameters, and ends with return format. Every sentence serves a purpose without redundancy.

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 the tool has no output schema, the description fully covers the return format. It explains all needed aspects: purpose, sub-actions, parameter usage, pagination, and return structure. The context is complete for effective tool selection and invocation.

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%—all parameters are described in the schema. The description adds extra context beyond the schema, such as advising to use the 'types' tool for type IDs and explaining the `external_id` parameter. This enhances usability, though the schema itself is already very clear.

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's purpose: to look up organizational hierarchy levels above units. It uses a specific verb ('Look up') and resource ('above units'), and distinguishes itself from the sibling 'units' tool by explicitly saying to use 'units' for unit-level entities.

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 provides explicit guidance: 'Use this for org hierarchy above the unit level. For units themselves... use the units tool instead.' It also lists sub-actions and mentions pagination, leaving no ambiguity about when to use this tool versus alternatives.

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