Skip to main content
Glama

Delete New Quiz

delete_new_quiz
DestructiveIdempotent

Permanently remove a New Quiz from a Canvas course using its assignment ID. This action cannot be undone, so confirm the correct course and assignment IDs.

Instructions

Delete a New Quiz (LTI) from a Canvas course. This action is permanent. Use assignment_id (not quiz_id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesThe Canvas course ID
assignment_idYesThe assignment ID of the New Quiz
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds the valuable explicit detail that 'This action is permanent.' It also clarifies the LTI-specific nature of the New Quiz object and the assignment_id requirement, giving the agent context beyond the raw destructive flag.

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?

Three short sentences, front-loaded with the primary action, with no filler. Every sentence contributes: resource/scope, permanence, and a critical identifier caveat.

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?

For a simple two-parameter delete with no output schema and strong annotations, the description covers the important operational facts (permanence and assignment_id). It is complete enough for the agent to invoke correctly, though it could have explicitly named sibling alternatives for fully unambiguous selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents both parameters with 100% coverage. The description adds meaningful clarification with 'Use assignment_id (not quiz_id),' which prevents a likely misuse when deleting New Quizzes; course_id semantics are adequately handled by 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?

Description opens with a specific action and object: 'Delete a New Quiz (LTI) from a Canvas course.' It also clarifies the correct identifier type ('Use assignment_id (not quiz_id)'), which distinguishes this deletion tool from quiz-item or classic-quiz deletion tools.

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 clearly scopes the tool to New Quiz (LTI) objects in a Canvas course, and the assignment_id note implies this is not the normal quiz_id-based path. However, it does not explicitly name alternatives (e.g., delete_assignment for regular assignments or delete_new_quiz_item for quiz items), so when-to-use versus siblings is only implied.

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