Skip to main content
Glama
Sign In
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quiz_questions

Read-onlyIdempotent

Retrieve all questions and question groups from a specified quiz set to review or manage educational content for exams.

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

NameRequiredDescriptionDefault
quizYesQuiz identification string

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.9
    • addedOutput schema / properties / items / items / properties / ai
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / items / items / properties / ai_reviewed
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
  2. 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)"
  3. 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"
+}
  4. First observedv1.0.22

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the domain hierarchy (questions inside quizzes, quizzes inside exams) which helps interpretation, but says nothing about ordering, pagination, or whether groups and questions are returned flat or nested.

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?

Two short sentences, front-loaded with the action and resource, zero filler. The second sentence is domain context rather than usage instruction, so it earns its place only partially.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one simple required parameter, full annotation coverage and an output schema, the description is adequate but minimal. It leaves open whether the call returns full question content or only identifiers/structure, which is the main thing an agent would want framed before calling.

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?

There is a single required 'quiz' parameter with 100% schema description coverage, so the schema already carries parameter documentation. The description only restates that the operand is a quiz set and adds no format, ID-source, or lookup guidance.

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?

Specific verb ('List') plus resource ('questions and question groups') scoped to 'in a Quiz set', which distinguishes it from the global edubase_get_questions and from mutation siblings like edubase_post_quiz_questions. It does not explicitly name those siblings, so the differentiation is inferred from the scoping phrase rather than stated.

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?

Usage is implied by the phrase 'in a Quiz set' and the hierarchy explanation (questions are the lowest level, quizzes are consumed by exams). There is no explicit when-to-use versus edubase_get_questions or edubase_get_question, and no stated prerequisite such as needing a quiz identifier from edubase_get_quizes.

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