Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

courses

Read-only

Query the course catalog and retrieve detailed course data including skills, students, lectures, exams, coupons, and invitations.

Instructions

Query the course catalog, course details, and course-related data including skills, students, lectures, exams, coupons, and invitations. Use this for course metadata, catalogs, and course-level data. For a specific user's course progress and completion status, use the dashboard tool with get_user_courses action. For browsing all content types (not just courses), use the content tool.

Sub-actions:

  • list: Search and filter the course catalog. Paginated.

  • list_user_courses: List courses for a specific user. Requires userId. Paginated.

  • list_categories: List course categories configured in the academy.

  • get: Get full details of a single course. Requires courseId.

  • get_skills: List skills taught by a course. Requires courseId.

  • get_students: List students enrolled in a course. Requires courseId. Paginated.

  • get_lectures: List lectures within a course. Requires courseId.

  • get_exams: List exams within a course. Requires courseId.

  • get_coupons: List coupons for a course. Requires courseId.

  • get_coupon: Get a specific coupon. Requires courseId and couponId.

  • get_invitations: List invitations for a course. Requires courseId.

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 course details, 'list_user_courses' for a user's courses, etc.
userIdNoUser ID. Required for: list_user_courses. Set external_id=true if passing an external ID.
external_idNoWhen true, treats userId as an external system ID instead of Schoox internal ID. Default: false. Used with list_user_courses.
roleNoFilter students by role: student, professor, or dropped_out. Used with get_students.
statusNoCourse status filter: active or archived. Default: active. Used with list.
searchNoSearch courses by name (e.g. 'Safety Training'). Used with list.
category_idNoCourse category ID (e.g. 1703). Use list_categories to discover available IDs. Used with list.
languageNoISO 639-1 language code to filter courses by content language (e.g. en, es, fr, de, ja, zh).
startNoStarting position for pagination (e.g. 0). Used with list, list_user_courses, get_students.
enrolledNoFilter to courses user is enrolled in: true or false. Used with list_user_courses.
limitNoMax results per page. Used with list, list_user_courses, get_students.
courseIdNoSchoox course ID (e.g. 327827). Required for: get, get_skills, get_students, get_lectures, get_exams, get_coupons, get_coupon, get_invitations.
onlyCompletedNoWhen true, returns only users who completed the course. Used with get_students.
couponIdNoCoupon ID. Required for: get_coupon (used with courseId to get a specific coupon).
skillsNoArray of skill/metric IDs to find related courses (e.g. [101, 205]). Used with list.
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces this with 'Query' disclosure. It adds behavioral details: pagination notes for list/list_user_courses/get_students, return format with truncated handling, and which parameters are required per sub-action.

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 well-structured: a concise overview paragraph, bullet list of sub-actions with key requirements, and return format. It is front-loaded with purpose and alternatives. Each sentence adds value; no fluff.

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 lacking an output schema, the description explains the return format ({ data, _meta}) and pagination/truncation behavior. It covers all sub-actions and their parameter dependencies. For a complex tool with 15 parameters, this is comprehensive.

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 15 parameters have descriptions). The description adds contextual semantics by mapping parameters to sub-actions (e.g., 'userId required for list_user_courses', 'external_id used with list_user_courses'), which helps agents apply parameters correctly.

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 uses a specific verb 'Query' and clearly identifies resources (course catalog, course details, etc.). It explicitly distinguishes from sibling tools 'dashboard' and 'content' by stating alternate use cases.

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 on when to use this tool versus alternatives ('for course metadata, catalogs, and course-level data') and directs to dashboard/content for other needs. Sub-actions are listed with required parameters, aiding correct invocation.

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