Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

curriculums

Read-only

Query structured training programs (learning paths) to retrieve metadata, enrollments, and student lists, with pagination and filters.

Instructions

Query learning paths (curricula) — collections of courses that form a structured training program. Use this for learning path metadata, enrollment, and student lists. For a user's completion progress across learning paths, use the dashboard tool with get_user_curriculums action.

Sub-actions:

  • list: Search and filter learning paths. Paginated.

  • list_user_curriculums: List learning paths for a specific user. Requires userId. Paginated.

  • get: Get full details of a single learning path. Requires curriculumId.

  • get_students: List students enrolled in a learning path. Requires curriculumId. Paginated.

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 catalog, 'get' for details, 'list_user_curriculums' for a user's paths, 'get_students' for enrollees
startNoStarting position for pagination (e.g. 0). Used with list, list_user_curriculums, get_students.
limitNoMax results per page. Used with list, list_user_curriculums, get_students.
statusNoLearning path status: active or archived. Default: active. Used with list.
external_idNoWhen true, treats userId as an external system ID instead of Schoox internal ID. Default: false. Used with list_user_curriculums.
userIdNoUser ID. Required for: list_user_curriculums. Set external_id=true if passing an external ID.
anyLanguageNoWhen true, returns all courses regardless of language. Default: false. Used with list_user_curriculums.
curriculumIdNoLearning path ID (e.g. 5001). Required for: get, get_students.
onlyCompletedNoWhen true, returns only users who completed the path. Used with get_students.
completionStartDateNoISO date string (e.g. 2024-01-01). Returns users who completed after this date. Used with get_students.
completionEndDateNoISO date string (e.g. 2024-12-31). Returns users who completed before this date. Used with get_students.
Behavior5/5

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

Annotations already indicate read-only and non-destructive. Description adds return format with _meta including truncated flag, plus guidance to apply filters/pagination when truncated. Contradictions: none.

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?

Well-structured: purpose, usage hint, sub-action list, return format. Front-loaded with key info. Could be slightly more concise but efficient overall.

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?

Complete for a multi-action read-only tool. Covers all sub-actions, return structure, pagination behavior, and distinguishes from sibling. No output schema but description explains return format adequately.

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%, baseline 3. Description provides context beyond schema by grouping parameters per sub-action and mentioning pagination. Adds organizational value, but schema already describes each param well.

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?

Description clearly states purpose: query learning paths for metadata, enrollment, student lists. Distinguishes from sibling 'dashboard' with get_user_curriculums for completion progress. Uses specific verbs and resource.

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?

Explicitly tells when to use this tool (learning path metadata, enrollment, student lists) and when not (user's completion progress, use dashboard instead). Also provides sub-actions and their contexts.

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