Canvas LMS MCP Server

Set Student New Quiz Accommodation

set_student_new_quiz_accommodation

Destructive

Instructions

Apply a time and/or attempts accommodation for a student across all New Quizzes in a course (course-level, single Canvas API call when no assignment_ids are given) or for a specified subset of New Quizzes (per-quiz fan-out when assignment_ids are given). New Quizzes use a time_multiplier (ratio, e.g. 1.5 for 1.5× time), not absolute minutes. For Classic Quizzes (quiz_type: assignment / practice_quiz / etc.) use set_student_quiz_accommodation instead. Partial per-quiz failures are tolerated — a failure on one quiz does not abort the rest. In per-quiz mode, fan-out is sequential (one Canvas API call per assignment ID, awaited in series). Canvas errors on the course-level path (no assignment_ids) propagate as a top-level error (no envelope). Returns a uniform envelope: scope ("course" or "per_quiz"), applied[], failed[], and summary. Provide user_id as the real Canvas user ID. If CANVAS_PSEUDONYMIZE_STUDENTS is enabled, call resolve_pseudonym first to obtain the real user_id from a pseudonym.

Input Schema

Name	Required	Description
`user_id`	Yes	Real Canvas user ID of the student to accommodate
`course_id`	Yes	Canvas course ID
`assignment_ids`	No	Limit accommodation to these specific New Quiz assignment IDs. Omit to apply a course-level accommodation (covers all New Quizzes in the course with a single Canvas API call). When provided, fans out one call per assignment ID.
`extra_attempts`	No	Additional attempts to grant beyond each quiz's default attempt limit.
`time_multiplier`	No	Time multiplier for New Quizzes (e.g. 1.5 for 1.5× time, 2.0 for double time). This is the native New Quizzes field; Canvas applies it to each quiz's time limit. Must be > 1.0. Mutually exclusive with nothing — can be combined with extra_attempts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.18.15Oct 14, 2026

addedInput schema / properties / assignment_ids / items / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / assignment_ids / items / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / assignment_ids / items / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / assignment_ids / items / type
```
Removed value: -"integer"
```

addedInput schema / properties / course_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / course_id / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / course_id / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / course_id / type
```
Removed value: -"integer"
```

addedInput schema / properties / user_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / user_id / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / user_id / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / user_id / type
```
Removed value: -"integer"
```

Changed1 schema field changedv1.18.11Sep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Addedv1.18.3Jul 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare only openWorldHint and destructiveHint; the description adds substantial beyond-annotation behavior: partial per-quiz failures are tolerated, fan-out is sequential and awaited in series, course-level errors propagate as a top-level error with no envelope, and the exact return envelope (scope, applied[], failed[], summary) is described.

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?

Dense but front-loaded: the course-level vs per-quiz split and the Classic-Quizzes reroute come first, followed by semantics, failure behavior, and return shape. Nearly every sentence carries load, though the description is long enough that it borders on crowding the primary routing guidance.

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

Completeness5/5

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

Despite no output schema, the description documents the return envelope, failure semantics, error propagation, and the pseudonym precondition. For a multi-mode mutation tool with external side effects, nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: it clarifies time_multiplier is a ratio native to New Quizzes (not absolute minutes), that it is combinable with extra_attempts, and that user_id must be the real Canvas user ID (obtainable via resolve_pseudonym).

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 (apply accommodation) plus the exact resource (student across New Quizzes in a course or a subset). It explicitly distinguishes two modes (course-level vs per-quiz) and names the sibling set_student_quiz_accommodation for Classic Quizzes, so an agent can route 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?

Gives explicit conditions: use this for New Quizzes, use set_student_quiz_accommodation for Classic Quizzes (assignment/practice_quiz/etc.), omit assignment_ids for course-level scope, and call resolve_pseudonym first when CANVAS_PSEUDONYMIZE_STUDENTS is enabled. Alternatives and preconditions are fully spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Set Student New Quiz Accommodation

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools