Skip to main content
Glama

delete_new_quiz_item

DestructiveIdempotent

Delete a specific item from a New Quiz in Canvas. This action permanently removes the question, requiring course, assignment, and item IDs.

Instructions

Delete an item (question) from a New Quiz (LTI). This action is permanent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesThe Canvas course ID
assignment_idYesThe assignment ID of the New Quiz
item_idYesThe New Quiz item ID (string, not numeric)
Behavior3/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 'This action is permanent,' which clarifies irreversibility. However, the idempotentHint may be confusing for a delete operation, and the description does not detail other behavioral effects (e.g., cascading on quiz scores).

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 concise sentences, front-loaded with the action. No unnecessary repetition. Could be slightly more structured by separating the warning, but overall efficient.

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 simple delete with 3 parameters and no output schema, the description is adequate but not comprehensive. Missing details like what happens on success, whether the quiz must exist, or any side effects. Sibling tools exist but description doesn't leverage that context.

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?

Input schema covers all three parameters with descriptive names and types (100% coverage). The description adds no additional semantics beyond the schema, so baseline 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?

Clearly states the tool deletes an item (question) from a New Quiz. Differentiates from siblings like delete_new_quiz (deletes the entire quiz) and delete_assignment (deletes an assignment). The specific mention of 'New Quiz (LTI)' distinguishes it from regular quiz items.

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?

No guidance on when to use this tool versus alternatives like delete_new_quiz or delete_assignment. The description is purely functional and does not mention prerequisites, context, or when not to use it.

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/bruchris/canvas-lms-mcp'

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