Skip to main content
Glama

set_student_assignment_dates

Destructive

Override due dates and availability for a specific student across all or selected assignments in a Canvas course.

Instructions

Fan a due-date / availability override for a specific student across all (or a filtered subset of) assignments in a course. Creates one student-set override per assignment via the Canvas assignment overrides API. Partial failures are tolerated — a failure on one assignment does not abort the rest. Note: for courses with many assignments this makes one Canvas API call per assignment. V1 is create-only: if an override for this student already exists on an assignment, Canvas returns a 422 and that assignment appears in the failed[] list. Use list_assignment_overrides to audit first. Dates must be ISO 8601 strings. To shift dates by a relative amount, first call list_assignments with include=overrides to retrieve current dates, compute absolute timestamps, then call this tool. Returns the standard fan-out envelope: separated applied[], skipped[] (unused in this create-only version, always empty), and failed[] (each with an error) arrays, a not_found list, and a summary of counts. Any assignment_ids that do not exist in the course are reported in not_found (they are neither applied nor failed). 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
titleNoLabel for each override (e.g. "Disability accommodation"). Defaults to "Student accommodation".
due_atNoNew due date in ISO 8601 format. Pass null to remove the due date.
lock_atNoAvailability close date in ISO 8601 format. Pass null to remove.
user_idYesReal Canvas user ID of the student to accommodate
course_idYesCanvas course ID
unlock_atNoAvailability open date in ISO 8601 format. Pass null to remove.
assignment_idsNoLimit the fan-out to these specific assignment IDs (provide at least one). Omit entirely to target all assignments in the course. IDs not present in the course are returned in not_found, not applied/failed.
Behavior5/5

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

Adds significant behavioral context beyond annotations: partial failure tolerance, create-only nature, error handling for existing overrides (422), not_found behavior, and return envelope structure. 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.

Conciseness3/5

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

The description is reasonably structured but somewhat lengthy. It front-loads the main purpose but includes many details that could be more concisely grouped. Adequate but not top-tier in conciseness.

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?

Given the tool complexity, the description covers all critical aspects: fan-out behavior, partial failure, create-only, error details, prerequisites, date format, return envelope with all fields, and user_id handling. No output schema exists, so the description carries full burden and does so thoroughly.

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?

Despite 100% schema coverage, the description adds operational context: explains title default, user_id must be real Canvas user ID, refers to resolve_pseudonym, clarifies assignment_ids behavior, and mandates ISO 8601 format.

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 it fans due-date/availability overrides for a specific student across assignments, using specific verbs like 'fan' and 'creates'. It distinguishes itself from sibling tools like quiz accommodations by focusing on assignments and describing the create-only nature.

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?

The description provides explicit when-to-use context, including preconditions like auditing via list_assignment_overrides, and alternatives for relative date shifts. It notes performance implications and that V1 is create-only. However, it does not explicitly state when NOT to use this tool for other scenarios.

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