Skip to main content
Glama
EduBase

EduBase MCP Server

Official
by EduBase
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edubase_post_quiz

Create a new quiz set to organize questions for practice or exams. Define title, mode, type, language, and optional settings.

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
quizYesQuiz identification string

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. 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"
+}
  3. First observedv1.0.22

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the agent knows this is a mutating, non-destructive, non-idempotent operation. The description adds the conceptual context of Quiz sets feeding into Exams but does not disclose additional behavioral details like permissions or side effects. It does not contradict annotations.

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 two concise sentences with no filler. It front-loads the core action and then adds a brief, relevant explanation of the resource type. Every word earns its place.

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 creation tool with a rich input schema (9 params), full schema coverage, and an output schema, the description adds the key context of how Quiz sets relate to Exams. It does not need to explain return values since an output schema exists. A minor gap is the lack of guidance on when to use different modes/types, but those are covered in the schema.

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?

With schema description coverage at 100%, all parameters are already documented in the schema. The description adds no extra parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action ('Create a new Quiz set') and defines what a Quiz set is, differentiating it from other entities like Exams by noting it can 'power multiple Exams'. This provides a specific verb and resource with useful context.

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 description implies usage by mentioning Quiz sets are 'used for practice or to power multiple Exams', giving some context for when to create one. However, it does not explicitly state when not to use this tool or mention alternatives, leaving the routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EduBase/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server