Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_get_quizes

Read-onlyIdempotent

List owned and managed quiz sets to access named collections of questions. Use search and pagination to filter results.

Instructions

List owned and managed Quiz sets. Quiz sets are named collections of questions that sit at the middle level of the EduBase Quiz hierarchy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage number (default: 1), not used in search mode!
limitNolimit number of results (default: 16)
searchNosearch string to filter results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedOutput schema / properties / quizes / items / properties / id / description
      Removed value: -"external unique Quiz identifier (if set for the Quiz)"
    • removedOutput schema / properties / quizes / items / properties / quiz / description
      Removed value: -"Quiz identification string"
    • removedOutput schema / properties / quizes / items / properties / title / description
      Removed value: -"title of the Quiz set"
  2. Changed3 schema fields changedv1.2.15
    • removedOutput schema / properties / quizes / items / properties / name
      Removed value: -{
-  "description": "title of the Quiz set",
-  "type": "string"
-}
    • addedOutput schema / properties / quizes / items / properties / title
      Added value: +{
+  "description": "title of the Quiz set",
+  "type": "string"
+}
    • changedOutput schema / properties / quizes / items / required
      Previous value: -[
-  "quiz",
-  "name"
-]New value: +[
+  "quiz",
+  "title"
+]
  3. Changed9 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "quizes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "external unique Quiz identifier (if set for the Quiz)"
+          },
+          "name": {
+            "description": "title of the Quiz set",
+            "type": "string"
+          },
+          "quiz": {
+            "description": "Quiz identification string",
+            "type": "string"
+          }
+        },
+        "required": [
+          "quiz",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "quizes"
+  ],
+  "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=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety. The description adds the behavioral scope constraint ('owned and managed') and explains what a quiz set is, but it does not mention pagination behavior, default limits, or result ordering, which would be useful for a list endpoint.

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 sentences, zero filler. The main action is front-loaded in the first sentence, and the second sentence provides necessary domain context without redundancy.

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 presence of an output schema and fully described parameters, the description adequately covers the tool's role. It explains the domain concept of a Quiz set and its position in the hierarchy. The only notable gap is the lack of explicit differentiation from closely related sibling tools, but this is not critical for a simple list operation.

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 every parameter (page, limit, search) already described in the input schema. The tool description adds no parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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 ('List'), a clear resource ('Quiz sets'), and a scope qualifier ('owned and managed'). The added hierarchy explanation ('middle level of the EduBase Quiz hierarchy') helps distinguish this from other quiz-related tools, though it does not explicitly name a sibling like edubase_get_quiz to differentiate.

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 on when to use this tool versus alternatives such as edubase_get_quiz or edubase_get_quiz_questions. The hierarchy mention implies a starting point for navigating quiz structures, but there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named.

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