Skip to main content
Glama
schoox

schoox-mcp-server

Official
by schoox

skills

Read-only

Query skill definitions, assessments, and relationships with jobs, courses, and users for competency management.

Instructions

Query skill/competency definitions, skill assessments, and the relationships between skills, jobs, courses, and users. Use this for competency management. To see what skills a course teaches, use the courses tool with get_skills action. To see a user's overall training progress (not just skills), use the dashboard tool.

Sub-actions:

  • list: List all skills/competencies with optional filtering by type or search term. Paginated.

  • get_job: List skills required for a specific job. Requires jobId.

  • get_user: Get a user's skill profile (all skills and levels). Requires userId.

  • get_user_skillAssessments: Get assessment results for a user on a specific skill. Requires skillId and userId.

  • get_jobs: List jobs that require a specific skill. Requires skillId. Paginated.

  • get_courses: List courses that teach a specific skill. Requires skillId. Paginated.

  • get_assessment: Get details of a single assessment. Requires assessmentId.

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 skill catalog, 'get_job' for job skills, 'get_user' for user skill profile, 'get_user_skillAssessments' for assessment results, 'get_jobs'/'get_courses' for skill relationships, 'get_assessment' for assessment details
typeIdNoFilter skills by metric type ID. Used with list.
searchNoSearch skills by name (e.g. 'Leadership'). Used with list.
external_idNoSkill external ID (string, not a boolean flag like other tools). Used with list to filter by external identifier.
startNoStarting position for pagination (e.g. 0). Used with list, get_jobs, get_courses.
limitNoMax results per page, up to 100. Default: 100. Used with list, get_jobs, get_courses.
jobIdNoJob ID (e.g. 201). Required for: get_job.
userIdNoUser ID (e.g. 12345). Required for: get_user, get_user_skillAssessments.
skillIdNoSkill ID (e.g. 501). Required for: get_user_skillAssessments, get_jobs, get_courses.
assessmentIdNoAssessment ID. Required for: get_assessment.
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds details on response format (JSON with _meta), pagination behavior, and the truncated flag, fully disclosing tool behavior 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with overall purpose, sibling disambiguation, and sub-action list. Information is front-loaded and each sentence serves a purpose, though slightly lengthy but justified by complexity.

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 the tool's complexity (multiple sub-actions, 10 parameters, no output schema), the description covers return format, pagination, truncated flag, and required params per action. Lacks examples but is highly complete.

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 has 100% description coverage, providing baseline 3. Tool description groups parameters by sub-action and clarifies which are required, adding value by mapping actions to parameters.

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 queries skill/competency definitions, assessments, and relationships. It differentiates from siblings by directing to courses/get_skills for course skills and dashboard for user training progress.

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 states when to use (competency management) and when not to (course skills, user progress), with named alternatives. Each sub-action includes required parameters for correct usage.

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