Skip to main content
Glama

edubase_post_quiz

Create quiz sets to organize questions for practice or exams. Specify a title and configure language, display mode, or copy from existing sets.

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
languageNodesired Quiz set language
titleYestitle of the Quiz set
idNoExternal unique Quiz identifier. Should be maximum 64 characters long!
descriptionNoshort description
copy_settingsNooptional Quiz set identification string to copy settings from
copy_questionsNooptional Quiz set identification string to copy questions from
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 - exam: for exam purposes - private: for private purposes (e.g testing)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYesQuiz identification string
Behavior2/5

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

Annotations are neutral (readOnlyHint=false, destructiveHint=false). The description only states 'Create', which aligns with mutation, but provides no further behavioral details such as required permissions, rate limits, side effects, or any constraints beyond the input schema.

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 extremely concise at two sentences, front-loading the action and purpose, with no redundant or wasted words.

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 complexity (8 parameters, enums) and presence of an output schema, the description provides sufficient context to understand the tool's role (creating quiz sets for practice or exams). It could mention the creation of a unique identifier or return value, but the output schema likely covers that.

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?

All 8 parameters have complete descriptions in the input schema (100% coverage). The tool description does not add any additional meaning beyond what the schema already provides, earning a baseline score of 3.

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 'Create a new Quiz set' with a specific verb and resource. It further explains what quiz sets are and how they are used ('collections of questions that can be used for practice or to power multiple Exams'), effectively distinguishing from sibling tools like edubase_post_question or edubase_post_exam.

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 gives a clear purpose but does not provide guidance on when to use this tool versus alternatives (e.g., edubase_post_question for individual questions, or edubase_post_exam for creating exams). It implies usage but lacks explicit when/when-not or alternative tool references.

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