Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Student Quiz Accommodation

set_student_quiz_accommodation
Destructive

Apply extra time and/or extra attempts to a specific student across all Classic Quizzes in a course (or a specified subset). Fans out to the Canvas quiz extensions API for each quiz.

Instructions

Apply extra time and/or extra attempts to a specific student across all Classic Quizzes in a course (or a specified subset). Fans out to the Canvas quiz extensions API for each quiz. New Quizzes (quiz_type quizzes.next) are skipped — use set_student_new_quiz_accommodation instead. Only applies to quizzes that exist at call time; re-run after creating new quizzes. Assignment due-date overrides are not handled here (separate fast-follow feature). Note: for courses with many quizzes this makes one Canvas API call per quiz. Partial failures are tolerated — a failure on one quiz does not abort the rest. Returns the standard fan-out envelope: separated applied[], skipped[] (each with a skip_reason), and failed[] (each with an error) arrays, a not_found list of any requested quiz_ids absent from the course, and a summary of counts. 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

NameRequiredDescriptionDefault
user_idYesReal Canvas user ID of the student to accommodate
quiz_idsNoLimit accommodation to these specific quiz IDs. Omit to target all Classic Quizzes in the course.
course_idYesCanvas course ID
extra_attemptsNoAdditional attempts to grant beyond the quiz default.
time_multiplierNoRelative time multiplier (e.g. 1.5 for 1.5× time). extra_minutes = round(quiz.time_limit * (multiplier - 1)), minimum 1 minute. Quizzes with no time limit are skipped for extra_time (extra_attempts is still applied if provided). Mutually exclusive with extra_time_minutes.
extra_time_minutesNoAbsolute extra time in minutes to add to each quiz. Mutually exclusive with time_multiplier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.18.15
    • 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 / quiz_ids / items / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / quiz_ids / items / exclusiveMinimum
      Removed value: -0
    • removedInput schema / properties / quiz_ids / items / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / quiz_ids / items / 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"
  2. 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"
  3. Addedv1.18.3

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations: discloses that it fans out one Canvas API call per quiz, that partial failures are tolerated without aborting the rest, and that pseudonymized student IDs require resolve_pseudonym first. This is exactly the operational context an agent needs before invoking a fan-out mutation.

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 and front-loaded: the core action and fan-out scope lead, followed by skip/edge-case routing. It is somewhat long, but nearly every sentence carries operational weight, with little redundancy.

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 fully describes the return envelope (applied[], skipped[] with skip_reason, failed[] with error, not_found, summary counts). Combined with the fan-out and pseudonymization caveats, an agent has everything needed to call and interpret this correctly.

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 reinforces key semantics: user_id must be the real Canvas ID, quiz_ids omission means 'all Classic Quizzes', and the time-limit-skip behavior for time_multiplier. Some of this duplicates the schema, but it adds the cross-field behavioral consequence (no-time-limit quizzes skipped for extra_time only).

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 extra time/attempts) and resource (student quiz accommodations across Classic Quizzes in a course), plus scope. It explicitly distinguishes itself from the sibling set_student_new_quiz_accommodation, which it names.

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 when/when-not and alternatives: New Quizzes (quizzes.next) are skipped and routed to set_student_new_quiz_accommodation, due-date overrides are out of scope, and quizzes list is frozen at call time so re-run after creating quizzes. Also names resolve_pseudonym as a prerequisite under CANVAS_PSEUDONYMIZE_STUDENTS.

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