Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quiz_questions

Read-onlyIdempotent

Retrieve all questions and question groups within a quiz set, providing a structured view of quiz content for exam preparation and review.

Instructions

List all questions and question groups in a Quiz set. Quiz sets contain questions (lowest level) and can be used by exams (highest level).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYesQuiz identification string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedOutput schema / properties / items / items / properties / active / description
      Removed value: -"active item"
    • removedOutput schema / properties / items / items / properties / group / description
      Removed value: -"question group title (if group)"
    • removedOutput schema / properties / items / items / properties / id / description
      Removed value: -"external unique question identifier (if question and present)"
    • removedOutput schema / properties / items / items / properties / question / description
      Removed value: -"question identification string (if question)"
  2. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active": {
+            "description": "active item",
+            "type": "boolean"
+          },
+          "group": {
+            "description": "question group title (if group)",
+            "type": "string"
+          },
+          "id": {
+            "description": "external unique question identifier (if question and present)",
+            "type": "string"
+          },
+          "question": {
+            "description": "question identification string (if question)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  3. First observedv1.0.22

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results include both questions and question groups and provides domain hierarchy context. It does not describe pagination, ordering, or nesting behavior, but the output schema and strong annotations lower the burden.

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?

Two short sentences with the action front-loaded. The second sentence adds useful domain context about quiz set hierarchy without padding. Every sentence earns its place, and there is no redundant wording.

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 required parameter and an output schema, the description is nearly sufficient. It tells the agent what it returns and how quiz sets relate to questions and exams. It does not explain exactly what a 'question group' is, but the output schema covers return structure, so no critical invocation detail is missing.

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?

Schema description coverage is 100%, with the 'quiz' parameter described as 'Quiz identification string.' The description reinforces that the quiz is a Quiz set, but provides no additional format, source, or lookup semantics beyond what the schema already offers. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'List all questions and question groups in a Quiz set.' It clearly scopes the operation to a quiz set, distinguishing it from global question tools like edubase_get_questions. It does not name sibling alternatives, so it misses the top tier, but the action and target are unambiguous.

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

Usage Guidelines3/5

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

The hierarchy note that 'Quiz sets contain questions' implies this tool is for retrieving question-level content within a quiz, which gives some usage context. However, it never explicitly tells the agent when to choose this over related tools like edubase_get_quiz, edubase_get_quiz_skills, or edubase_get_questions, nor does it state any exclusions.

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