Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update New Quiz

update_new_quiz
DestructiveIdempotent

Modify an existing New Quiz in a Canvas course: change title, availability dates, points, instructions, or publish status.

Instructions

Update an existing New Quiz (LTI) in a Canvas course.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoTitle of the quiz
due_atNoISO-8601 due date (null to clear)
lock_atNoISO-8601 lock time (null to clear)
course_idYesThe Canvas course ID
publishedNoWhether the quiz is visible to students
unlock_atNoISO-8601 unlock time (null to clear)
instructionsNoHTML instructions shown before the quiz starts
assignment_idYesThe assignment ID of the New Quiz
points_possibleNoTotal points

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed8 schema fields changedv1.18.8
    • removedInput schema / properties / due_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / due_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / instructions / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / instructions / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / lock_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / lock_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / unlock_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / unlock_at / type
      Added value: +[
+  "string",
+  "null"
+]
  3. First observedv1.18.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations include destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description adds no behavioral context beyond these flags. It does not clarify what 'update' entails (e.g., whether unspecified fields are reset, permission requirements, or the impact of destructive behavior). The description adds no value beyond 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no fluff or redundant information. It is front-loaded with the action and resource, making it easy to parse. No unnecessary words are present.

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

Completeness2/5

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

For a tool with 9 parameters and no output schema, the description is far too brief. It does not explain update semantics (e.g., whether omitted fields are preserved or reset), the significance of the required identifiers, or any potential side effects. Given the complexity and annotations, the description leaves critical operational details to inference.

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 all 9 parameters are documented in the schema. The description does not add any additional meaning or context to the parameters, such as how they interact or which are commonly used together. Baseline score of 3 is appropriate given full schema coverage.

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 action ('Update'), the resource ('New Quiz (LTI)'), and the context ('in a Canvas course'). It distinguishes from create_new_quiz and delete_new_quiz, making the tool's purpose unambiguous even without inspecting the schema.

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?

The description provides no guidance on when to use this tool versus alternatives like update_assignment or update_course. It does not mention prerequisites, exclusions, or conditions that would select this tool over siblings.

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