Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quiz_skills

Read-onlyIdempotent

Retrieve the skills associated with a quiz set, including each skill's identifier, title, and description. Use this to identify learning objectives covered by a quiz.

Instructions

Get the skills defined in a Quiz set, with the identifier, title and description of each skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYesQuiz identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYes
skillsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / quiz / description
      Removed value: -"Quiz 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the specific return fields (identifier, title, description) but doesn't disclose other behaviors like pagination or authentication requirements. Since annotations handle the core safety context, this is acceptable.

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, concise sentence that front-loads the primary action and return content. No filler or redundant information.

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 operation with one parameter and an output schema, the description is sufficiently complete. It covers the purpose and return fields; annotations handle safety. The only minor gap is the lack of clarification on what constitutes a 'Quiz set', but this is likely domain knowledge.

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 single parameter 'quiz' is fully documented in the schema with the description 'Quiz identification string'. The tool description adds no extra meaning beyond what the schema provides, so the baseline score of 3 applies for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: retrieve skills defined in a Quiz set, with specific fields (identifier, title, description). It distinguishes from exam-related skills by explicitly mentioning 'Quiz set', though it doesn't reference the sibling edubase_get_exam_skills or other similar tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like edubase_get_exam_skills or edubase_get_quiz. The description only states what it does without indicating prerequisites, exclusions, or selection criteria.

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