Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

content

Read-only

Browse and filter learning content items and metadata including categories, venues, and timezones.

Instructions

Browse content items (web resources, uploaded files, SCORM packages) and related metadata such as categories, venues, and timezones. Use this for browsing all content types and content metadata. For course-specific data (skills, students, lectures, exams), use the courses tool instead.

Sub-actions:

  • list: List content items with filtering by type, sub-type, category, tags, or search term. Supports pagination and sorting.

  • list_categories: List content categories configured in the academy. Useful for discovering category IDs to filter content.

  • list_venues: List venues (physical locations for events). Supports pagination and search.

  • list_timezones: List available timezones for scheduling.

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 content items, 'list_categories' for content categories, 'list_venues' for venues, 'list_timezones' for timezones
startNoStarting position for pagination (e.g. 0). Used with list and list_venues actions.
limitNoNumber of items to return per request. Default: 20, max: 20. Used with list and list_venues actions.
order_byNoSort field for content items: 'title', 'time_added', or 'time_modified'. Default: 'time_added'. Used with list action.
directionNoSort direction: 'asc' (ascending) or 'desc' (descending). Default: 'desc'. Used with list action.
category_idNoFilter content items by category ID (e.g. 1703). Use list_categories to discover available IDs. Used with list action.
type_idNoContent type filter: '1' = Web Resources, '2' = Files. Used with list action.
sub_type_idNoContent sub-type filter: 1=Online Video, 2=Online Document, 3=Online Article, 4=Online Photo, 5=Academic Link, 6=Website, 7=Document, 8=Video, 9=Image, 10=Audio, 11=SCORM. Used with list action.
tagsNoFilter content items by tags (e.g. 'managers' or 'Tag1,Tag2' for multiple). Used with list action.
searchNoSearch content items by name (e.g. 'Safety Training'). Used with list and list_categories actions.
Behavior4/5

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

Annotations already indicate read-only and non-destructive nature. Description adds value by detailing return JSON format, including the truncated flag and meta structure, which helps the agent understand pagination behavior.

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?

Description is efficiently structured with a clear main purpose, followed by sub-action list and return format. No redundant phrases, but could be slightly more compact by omitting 'Use this for' repetition.

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

Completeness4/5

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

Given 10 parameters and 4 sub-actions without output schema, the description covers return format, pagination, filter usage, and truncation handling. It sufficiently explains how to navigate the tool's capabilities.

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?

Input schema provides 100% parameter descriptions. Description adds grouping of parameters per sub-action and explains the purpose of category_id discovery via list_categories. However, the schema already carries most of the semantic load.

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 browses content items and metadata, distinguishes it from the courses tool, and lists specific sub-actions. The verb 'browse' and resource 'content items, categories, venues, timezones' 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?

Explicitly says when to use ('browsing all content types') and when not ('For course-specific data, use courses instead'), providing a direct alternative. Also explains each sub-action's 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