Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_exam_skills

Read-onlyIdempotent

Retrieve the skills defined in an exam's quiz set, including each skill's identifier, title, and description.

Instructions

Get the skills defined in the Quiz set used by an exam, with the identifier, title and description of each skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesexam identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYes
skillsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / exam / description
      Removed value: -"exam identification string"
    • removedOutput schema / properties / skills / items / properties / description / description
      Removed value: -"skill description (if set)"
    • removedOutput schema / properties / skills / items / properties / identifier / description
      Removed value: -"skill identifier"
    • removedOutput schema / properties / skills / items / properties / title / description
      Removed value: -"title of the skill"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / skills / items / properties / name
      Removed value: -{
-  "description": "skill name",
-  "type": "string"
-}
    • addedOutput schema / properties / skills / items / properties / title
      Added value: +{
+  "description": "title of the skill",
+  "type": "string"
+}
    • changedOutput schema / properties / skills / items / required
      Previous value: -[
-  "identifier",
-  "name"
-]New value: +[
+  "identifier",
+  "title"
+]
  3. Addedv1.2.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral nuance that skills are retrieved indirectly through the exam's quiz set, which is useful context beyond the annotations. No contradiction exists.

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 a single, well-structured sentence that begins with the action verb and directly states the resource and returned fields. There is no redundant wording, and all content earns its place.

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?

For a simple read-only tool with one parameter and an output schema, the description adequately covers what the tool does and what it returns. Minor gaps, such as behavior when the exam has no quiz set, are not critical for an agent to invoke it correctly. The existence of an output schema relieves the description of explaining return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description for the 'exam' parameter is 100% covered ('exam identification string'). The tool description does not add additional meaning about the parameter beyond what the schema provides; it merely reflects the same identification role. Baseline 3 is appropriate given the high schema coverage.

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 states a specific verb ('Get'), a precise resource ('skills defined in the Quiz set used by an exam'), and enumerates the returned fields (identifier, title, description). It clearly distinguishes itself from the sibling tool edubase_get_quiz_skills by specifying the indirection through an exam.

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 provides clear context: this tool retrieves skills from the quiz set associated with an exam, implying it is the correct choice when the entry point is an exam rather than a quiz. However, it does not explicitly mention alternatives or exclusion criteria, so it stops short of a full usage guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools