Skip to main content
Glama

edubase_post_quiz

Create a new quiz set to group questions for practice sessions or to power multiple exams.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "edubase_post_quiz"
  }
}

Input 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, the user must answer each before moving to the next - MINI: like TURNS, choice and multiple-choice questions only, needs the Mini Quiz feature
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

NameRequiredDescriptionDefault
quizYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.15
    • changedInput schema / properties / mode / description
      Previous 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"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, the user must answer each before moving to the next - MINI: like TURNS, choice and multiple-choice questions only, needs the Mini Quiz feature"
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "TEST",
      -  "TURNS"
      -]New value: +[
      +  "TEST",
      +  "TURNS",
      +  "MINI"
      +]
  2. Changed1 schema field changedv2.0.0
    • removedOutput schema / properties / quiz / description
      Removed value: -"Quiz identification string"
  3. 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"
      +]
  4. 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"
      +}
  5. First observedv1.0.22

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description is not obligated to restate them. It adds domain context about what a Quiz set is but says nothing beyond the annotations about creation semantics, the effect of copying settings/questions from another set, or what the openWorld/organization behavior implies. Adequate but not additive on behavior.

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 then the resource definition, with no filler or redundancy. It is efficient, though the second sentence is conceptual rather than actionable for a caller.

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?

The tool is a 9-parameter creation call, but the input schema is fully documented, has an output schema, and annotations cover the mutation semantics, so the description does not need to explain fields or return values. What remains missing is a pointer to the read/update siblings and the creation-only scope versus edubase_patch_quiz, a minor gap given the rich structured data.

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% across all 9 parameters, including enum explanations for mode and type, so the schema carries the parameter burden and baseline 3 applies. The description contributes nothing about any individual parameter, so it neither compensates for nor duplicates the schema.

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 opens with a specific verb+resource ("Create a new Quiz set") and follows with a one-line definition of what a Quiz set is, which an agent can distinguish from the exam-oriented siblings. It stops short of naming any sibling (e.g. edubase_post_exam, edubase_patch_quiz) as the alternative, so differentiation is conceptual rather than explicit.

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 clause "can be used for practice or to power multiple Exams" hints at the domain purpose but gives no when-to-use guidance, no condition that selects this tool over edubase_post_exam or edubase_patch_quiz, and no prerequisites such as permissions or the organization constraint. The agent is left to infer usage entirely from the name.

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