Skip to main content
Glama

Update New Quiz Item

update_new_quiz_item
DestructiveIdempotent

Update a specific question in a New Quiz by supplying only the fields to change—supports choice, true-false, essay, matching, and numeric types, plus position and points.

Instructions

Update an existing item (question) in a New Quiz (LTI). All fields are optional; supply only what changes. Canvas may rate-limit rapid sequential updates. Call serially (not in parallel). For >50 items, chunk and pause between batches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
item_idYesThe New Quiz item ID (string, not numeric)
positionNoUpdated 1-based position
course_idYesThe Canvas course ID
assignment_idYesThe assignment ID of the New Quiz
points_possibleNoUpdated point value
Behavior4/5

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

Annotations already declare idempotent and destructive hints. The description adds valuable context about rate limiting and suggested batching, which goes beyond structured metadata. Does not contradict annotations.

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, no redundancy. Front-loaded with the core purpose, followed by actionable usage notes. 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?

For a tool with a complex item schema, the description focuses on operational aspects (serial calls, batching) that are not covered by schema or annotations. It could mention that different interaction types have different required fields, but that's already in the schema. No output schema exists, but the description doesn't need to explain returns.

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?

Schema coverage is 83%, so parameters are largely documented. The description adds the crucial insight that all fields are optional and only changed fields need to be supplied, which is not explicit in the schema for partial updates.

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 it updates an existing item (question) in a New Quiz, using a specific verb and resource. Distinguishes from siblings like create_new_quiz_item, delete_new_quiz_item, and get_new_quiz_item by focusing on modification.

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?

Gives explicit guidance on serial calls, chunking for >50 items, and handling rate limits. While it doesn't explicitly contrast with alternatives, the context and purpose make usage clear.

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