Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

events

Read-only

Query and list instructor-led training and virtual classroom events, including session offerings, attendees, and attendance data.

Instructions

Query instructor-led training (ILT) and virtual classroom (VC) events -- sessions, offerings, attendees, and attendance data. Use this for scheduled training events. ILT = in-person sessions; VC = virtual/online sessions. Both types share the same parameter patterns but use separate actions (e.g. list_ilt vs list_vc).

Sub-actions: ILT (in-person):

  • list_ilt: List ILT events with optional date/status filters. Paginated.

  • get_ilt: Get details of a single ILT event. Requires eventId.

  • get_ilt_offers: List session offerings for an ILT event. Requires eventId. Paginated.

  • get_ilt_addOffers: List additional session offerings for an ILT event. Requires eventId. Paginated.

  • get_ilt_users: List attendees of an ILT event. Requires eventId. Paginated.

  • get_ilt_usersAttendanceData: Get attendance records for an ILT event. Requires eventId. Paginated. VC (virtual):

  • list_vc: List VC events with optional date/status filters. Paginated.

  • get_vc: Get details of a single VC event. Requires eventId.

  • get_vc_offers: List session offerings for a VC event. Requires eventId. Paginated.

  • get_vc_users: List attendees of a VC event. Requires eventId. Paginated.

  • get_vc_usersAttendanceData: Get attendance records for a VC event. Requires eventId. 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. ILT actions: list_ilt, get_ilt, get_ilt_offers, get_ilt_addOffers, get_ilt_users, get_ilt_usersAttendanceData. VC actions: list_vc, get_vc, get_vc_offers, get_vc_users, get_vc_usersAttendanceData.
dateStartNoDate filter start (e.g. 2024-01-01). Used with list_ilt, list_vc to filter events by date range.
dateEndNoDate filter end (e.g. 2024-12-31). Used with list_ilt, list_vc to filter events by date range.
startNoStarting position for pagination (e.g. 0). Used with list_ilt, list_vc.
limitNoMax events per page. Default: 20. Used with list_ilt, list_vc.
statusNoEvent status: active, archived, or canceled. Default: active. Used with list_ilt, list_vc.
eventIdNoEvent ID (e.g. 3001). Required for all get_ilt_* and get_vc_* actions.
onlyCompletedNoWhen true, returns only users who completed the event (includes certificate date). Used with get_ilt_users, get_vc_users.
searchNoSearch events by name. Used with list_ilt, list_vc.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, which the description supports by stating it queries data. The description adds behavioral details: pagination, truncation indicator, and return JSON structure, exceeding annotation coverage.

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?

The description is well-organized with bullet points and clear separation of ILT and VC sub-actions. It is longer but front-loaded with overall purpose. Could trim some redundancy, but structure aids readability.

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 9 parameters and 11 actions, the description covers all sub-actions, parameter applicability, pagination, truncation, and return format. No output schema exists, but the description compensates with detailed JSON structure explanation.

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 baseline is 3. The description adds context beyond schema by explaining parameter usage (e.g., 'Date filter start (e.g. 2024-01-01)') and specifying which actions each parameter applies to. This adds meaningful value.

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 explicitly states it queries instructor-led training (ILT) and virtual classroom (VC) events, listing specific sub-actions for each type. It clearly distinguishes between ILT and VC, making purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description details when to use each sub-action (e.g., 'Requires eventId' for gets, 'Used with list_ilt/list_vc' for filters) and explains pagination via start/limit parameters. While it doesn't compare to sibling tools, usage context is sufficiently clear.

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