Skip to main content
Glama

set_student_new_quiz_accommodation

Destructive

Apply time multiplier and extra attempts accommodations to a student for New Quizzes in Canvas – course-wide or for specific quizzes.

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

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesReal Canvas user ID of the student to accommodate
course_idYesCanvas course ID
assignment_idsNoLimit 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_attemptsNoAdditional attempts to grant beyond each quiz's default attempt limit.
time_multiplierNoTime 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.
Behavior5/5

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

Beyond annotations (destructiveHint: true, openWorldHint: true), the description reveals key behaviors: time_multiplier is a ratio (not absolute minutes), partial per-quiz failures are tolerated, fan-out is sequential, course-level errors propagate directly, and return envelope structure is provided. No contradictions with annotations.

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?

The description is moderately long but well-organized, starting with core purpose, then clarifying details about time_multiplier, alternatives, failure handling, return envelope, and prerequisites. Every sentence adds essential information; no fluff. Could be slightly more concise without losing clarity.

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?

Given the presence of annotations, full parameter documentation, and no output schema, the description covers input behavior, multiple modes, error handling, and return format adequately. Minor omissions: no explicit upper bound for time_multiplier, but overall complete for an AI agent to invoke 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%, but the description adds valuable context: time_multiplier is a native New Quizzes field (must be >1.0), extra_attempts adds beyond default, assignment_ids toggle between course-level and per-quiz modes, and user_id must be real (with pseudonym resolution hint). This goes beyond schema descriptions.

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 tool applies time and/or attempts accommodations for New Quizzes, distinguishing between course-level (single API call) and per-quiz (fan-out) modes. It specifies 'New Quizzes' and contrasts with Classic Quizzes, making the purpose and scope unambiguous.

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?

The description explicitly tells when to use this tool versus alternatives (Classic Quizzes → set_student_quiz_accommodation), explains the two modes with conditions (assignment_ids present or absent), and warns about pseudonymization prerequisites. It also describes when to use resolve_pseudonym first.

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