Skip to main content
Glama

edubase_delete_quiz_questions

DestructiveIdempotent

Remove specific questions from a quiz set or a question group by providing quiz ID, optional group title, and comma-separated question IDs.

Instructions

Remove question(s) from a Quiz set, or one of its question group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quizYesQuiz identification string
groupNoquestion group title
questionsYescomma-separated list of question identification strings
Behavior2/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds no extra behavioral context, such as whether questions are permanently deleted or just removed from the quiz, or any side effects. It relies heavily on 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 a single concise sentence that is front-loaded with the action and resource. It could be slightly clearer by explicitly stating the parameters, but it is not verbose or wasteful.

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

Completeness3/5

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

For a destructive tool with no output schema, the description is somewhat complete but lacks context about prerequisites (e.g., quiz existence) and related tools like edubase_get_quiz_questions. It does not mention what happens when questions are removed from a quiz (e.g., are they still available in the question bank?).

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?

The input schema has 100% coverage with clear descriptions for each parameter. The description adds context that the optional 'group' parameter allows removal from a specific question group, which aligns with the schema. However, it does not explain how to obtain group titles or the format of question IDs beyond the schema.

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 tool removes questions from a quiz or a specific question group, using specific verbs and resources. It distinguishes from siblings like edubase_delete_question (which deletes questions entirely) and edubase_delete_quiz (which deletes the quiz).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the tool is used to remove questions from a quiz or question group, providing clear usage context. However, it does not explicitly state when not to use it or mention alternatives, such as edubase_post_quiz_questions for adding questions.

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