Get Canvas calendar events and assignments for selected courses or users, with date filtering and event type options.
List Canvas calendar events or assignments across selected contexts (courses/users).
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| endDate | No | ||
| allEvents | No | ||
| startDate | No | YYYY-MM-DD or ISO 8601. | |
| contextCodes | No | Array like ["course_123", "user_456"]. |
Changes observed during successful MCP inspections.
v2.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.2.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers the safety profile, and the description adds the context-scoping behavior ('across selected contexts'). It does not disclose return format, pagination, or how allEvents affects results, but it does not contradict the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. Every word contributes to the basic understanding of the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 5-parameter tool with no output schema and many siblings, this description is too minimal. It omits date handling semantics, allEvents behavior, default type, and how it differs from canvas_list_assignments.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 40%, and the description does little to compensate. It paraphrases contextCodes as 'selected contexts' but leaves endDate, allEvents, and type defaults undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List'), resource ('Canvas calendar events or assignments'), and scope ('across selected contexts'). However, it does not differentiate from overlapping siblings like canvas_list_assignments or canvas_list_upcoming_events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. The overlap with canvas_list_assignments is not addressed, and there are no explicit exclusions or conditions for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.