Skip to main content
Glama

Delete Quiz Question

delete_quiz_question
DestructiveIdempotent

Permanently delete a single question from a Classic quiz. Classic Quizzes only; use delete_new_quiz_item for a New Quiz item.

Instructions

Permanently delete a single question from a Classic quiz. Classic Quizzes only; use delete_new_quiz_item for a New Quiz item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quiz_idYesThe Canvas quiz ID (Classic Quizzes only)
course_idYesThe Canvas course ID
question_idYesThe Canvas quiz question ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.15

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds the irreversibility qualifier 'permanently' and the Classic-quiz-only restriction, which sharpens the blast radius. It does not, however, add anything about side effects on existing submissions or whether the deletion is recoverable.

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?

Two sentences, zero filler, with the destructive action front-loaded and the disambiguation clause placed immediately after. 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?

With no output schema needed for a delete and all three required params documented, the definition is nearly complete; annotations carry the safety profile. The only missing nuance is the downstream effect of removing a question from an already-administered quiz.

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 course_id, quiz_id and question_id are already documented in the schema. The description adds no format, ordering, or referential detail (e.g. that question_id must belong to quiz_id) beyond what the structured fields provide. Baseline 3 applies.

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?

States a specific verb ('Permanently delete'), the exact resource ('a single question'), and the scope ('from a Classic quiz'). It also names the sibling it must not be confused with, delete_new_quiz_item, so the agent can distinguish it without opening either schema.

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

Usage Guidelines5/5

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

Explicitly states the applicability constraint ('Classic Quizzes only') and the routing alternative ('use delete_new_quiz_item for a New Quiz item'). Both the when and the when-not are given, leaving nothing to inference.

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