Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

users

Read-only

Search and retrieve user profiles and badges from Schoox. Get identity data like name, email, role, and organizational placement.

Instructions

Look up Schoox user profiles and badges. Use this for identity data (name, email, role, organizational placement). For training progress, course completions, and analytics, use the dashboard tool instead.

Sub-actions:

  • list: Search and filter users by role, org unit, job, or search term. Paginated.

  • get: Get full profile for one user. Requires userId. Accepts Schoox ID, external ID (set external_id=true), or email (set is_email=true).

  • get_badges: List badges earned by a user. Requires userId.

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 user search, 'get' for one user's profile, 'get_badges' for earned badges
userIdNoUser identifier (e.g. 12345). Required for: get, get_badges. Accepts Schoox user ID, external ID (set external_id=true), or email (set is_email=true).
external_idNoWhen true, treats userId as an external system ID instead of Schoox internal ID. Default: false.
is_emailNoWhen true, treats userId as an email address for lookup. Default: false.
roleNoFilter by user role: employee, customer, instructor, or member. Used with list.
pastNoInclude past/terminated employees. Only applies when role=employee. Default: false.
searchNoSearch by first name, last name, email, or username. Used with list.
aboveIdNoFilter by Above Unit ID (e.g. region/division). Used with list.
unitIdNoFilter by Unit ID (e.g. store/location). Used with list.
jobIdNoFilter by Job ID. Used with list.
startNoStarting position for pagination (e.g. 0). Used with list.
limitNoMax users per page, up to 1000. Default: 100. Used with list.
Behavior4/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds behavioral context beyond annotations by detailing the return format (JSON with _meta) and the truncated flag behavior. It also explains how to handle pagination when results are truncated.

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, with a clear opening sentence, then bullet-style lists for sub-actions and parameter notes. It front-loads the primary purpose and alternative tool, making it easy for an agent to quickly understand usage.

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?

Despite having 12 parameters and no output schema, the description covers return format, pagination, and truncation behavior. Combined with the detailed schema, it provides complete guidance for an agent to invoke the tool correctly.

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%, so all parameters are described. The description adds meaning by grouping parameters by sub-action and explaining the userId acceptance logic (Schoox ID, external ID, email). This provides context beyond the schema's type 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's purpose: to look up Schoox user profiles and badges. It distinguishes from sibling tools like 'dashboard' by specifying that for training progress and analytics, the dashboard tool should be used instead. The sub-actions (list, get, get_badges) further clarify the specific capabilities.

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 states when to use this tool ('identity data') and when not to ('training progress... use dashboard instead'). It also provides guidance on sub-actions and parameter usage, such as requiring userId for 'get' and 'get_badges', and listing filters for 'list'.

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