Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

exams

Read-only

List exams, get all student scores for a specific exam, or retrieve one user's score. Returns exam metadata and results.

Instructions

Query exam metadata and student exam results/scores. Use this for exam catalogs and per-exam student scores. For a specific user's exam history across all exams, use the dashboard tool with get_user_exams action.

Sub-actions:

  • list: List all exams in the academy. Paginated.

  • get_students: List all students who took a specific exam with their scores. Requires examId. Paginated.

  • get_student: Get one user's score for a specific exam. Requires examId and 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 exam catalog, 'get_students' for all scores on an exam, 'get_student' for one user's score
startNoStarting position for pagination (e.g. 0). Used with list, get_students.
limitNoMax students per page, up to 100. Default: 100. Used with list, get_students.
examIdNoExam ID (e.g. 8001). Required for: get_students, get_student.
userIdNoUser ID or external ID. Required for: get_student (returns one user's score for a specific exam).
Behavior5/5

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

Annotations already indicate read-only, non-destructive. Description adds return format details (data, _meta with truncation flag) and pagination behavior, providing full transparency beyond annotations.

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?

Front-loaded with purpose, structured with bullet list for sub-actions, return format note. No redundant sentences.

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?

For a 5-parameter, 3-action tool with no output schema, description covers return format, pagination, truncation behavior, and required params per action. Complete given annotations.

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 covers all parameters with descriptions (100% coverage). Description adds value by grouping parameters per sub-action and clarifying required contexts, elevating beyond baseline 3.

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 it queries exam metadata and scores, distinguishes from sibling dashboard tool for user exam history. Verb 'query' is specific, resource is exams.

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 (exam catalogs, per-exam scores) and when to use sibling tool (dashboard for user's exam history), and references specific action.

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