Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edubase_post_quiz

Create a quiz set to organize questions for practice or exams. Configure title, mode, type, language, and optional copy settings to build reusable question collections.

Instructions

Create a new Quiz set. Quiz sets are collections of questions that can be used for practice or to power multiple Exams.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExternal unique Quiz identifier. Should be maximum 64 characters long!
modeNoSets how questions are displayed during the Quiz. (default: TEST) - TEST: all questions are displayed at once, user can answer them in any order and switch between them - TURNS: questions are displayed one by one, only one question is visible at a time and the user must answer it before moving to the next question
typeNoType of the Quiz set. (default: set) - set: for practice purposes - final: for course exam purposes - exam: for exam purposes - private: for private purposes (e.g testing)
titleYestitle of the Quiz set
languageNodesired Quiz set language
descriptionNoshort description
organizationNoorganization identification string to assign the Quiz set to, only an organization of the API application owner can be used, always the organization of the user for organizational members
copy_settingsNooptional Quiz set identification string to copy settings from
copy_questionsNooptional Quiz set identification string to copy questions from

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • removedOutput schema / properties / quiz / description
      Removed value: -"Quiz identification string"
  2. Changed3 schema fields changedv1.2.15
    • addedInput schema / properties / organization
      Added value: +{
+  "description": "organization identification string to assign the Quiz set to, only an organization of the API application owner can be used, always the organization of the user for organizational members",
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Type of the Quiz set. (default: set) - set: for practice purposes - exam: for exam purposes - private: for private purposes (e.g testing)"New value: +"Type of the Quiz set. (default: set) - set: for practice purposes - final: for course exam purposes - exam: for exam purposes - private: for private purposes (e.g testing)"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "set",
-  "exam",
-  "private"
-]New value: +[
+  "set",
+  "final",
+  "exam",
+  "private"
+]
  3. Changed11 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / copy_questions
      Added value: +{
+  "description": "optional Quiz set identification string to copy questions from",
+  "type": "string"
+}
    • addedInput schema / properties / copy_settings
      Added value: +{
+  "description": "optional Quiz set identification string to copy settings from",
+  "type": "string"
+}
    • changedInput schema / properties / id / description
      Previous value: -"External unique Quiz identifier.\nShould be maximum 64 characters long!"New value: +"External unique Quiz identifier. Should be maximum 64 characters long!"
    • addedInput schema / properties / id / maxLength
      Added value: +64
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedInput schema / properties / mode / description
      Previous value: -"Sets how questions are displayed during the Quiz. (default: TEST)\n- TEST: all questions are displayed at once, user can answer them in any order and switch between them\n- TURNS: questions are displayed one by one, only one question is visible at a time and the user must answer it before moving to the next question\n"New value: +"Sets how questions are displayed during the Quiz. (default: TEST) - TEST: all questions are displayed at once, user can answer them in any order and switch between them - TURNS: questions are displayed one by one, only one question is visible at a time and the user must answer it before moving to the next question"
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "TEST",
+  "TURNS"
+]
    • changedInput schema / properties / type / description
      Previous value: -"Type of the Quiz set. (default: set)\n- set: for practice purposes\n- exam: for exam purposes\n- private: for private purposes (e.g testing)\n"New value: +"Type of the Quiz set. (default: set) - set: for practice purposes - exam: for exam purposes - private: for private purposes (e.g testing)"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "set",
+  "exam",
+  "private"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "quiz": {
+      "description": "Quiz identification string",
+      "type": "string"
+    }
+  },
+  "required": [
+    "quiz"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.22

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-idempotent (idempotentHint=false). The description adds no extra behavioral context such as permissions, side effects, or the fact that it returns a new resource ID. It simply states the creation action, which is already implied by the annotations.

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?

The description is two sentences with the action front-loaded and a brief definition following. It is concise and avoids unnecessary detail, though it could be slightly richer without becoming verbose.

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

Completeness2/5

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

For a creation tool with 9 parameters and an output schema, the description is minimal. It doesn't explain when to create a quiz set versus an exam, any prerequisites, or typical use cases beyond the short definition. The existence of an output schema covers return values, but the description still lacks operational context that would help an agent decide to invoke it.

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%, so every parameter is documented in the schema itself. The description does not add any parameter-specific meaning beyond that baseline, so a 3 is appropriate per the scoring rule.

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 'Create' and the resource 'Quiz set', and adds a definition that distinguishes it from exams. It doesn't explicitly name siblings like post_exam, but the resource is specific enough to avoid confusion.

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?

The description provides no guidance on when to use this tool versus alternatives such as edubase_post_exam or edubase_post_question. It only defines what a quiz set is, leaving the selection decision to the agent without explicit context.

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