Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Calendar Events

list_calendar_events
Read-only

List calendar events for a course, unbounded by the ~1-week/20-item caps that get_upcoming_events and get_my_upcoming_assignments are stuck with.

Instructions

List calendar events for a course, unbounded by the ~1-week/20-item caps that get_upcoming_events and get_my_upcoming_assignments are stuck with. By default Canvas only returns type="event" items for today alone (end_date defaults to start_date) — pass both start_date and end_date to cover a range, and type="assignment" to list assignment due dates instead of plain events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoKind of calendar item to return. Defaults to "event" if omitted.
end_dateNoInclusive range end (YYYY-MM-DD or ISO 8601 datetime). Defaults to start_date if omitted — i.e. a single day. Set this explicitly whenever you want more than one day.
course_idYesThe Canvas course ID
start_dateNoInclusive range start (YYYY-MM-DD or ISO 8601 datetime). Defaults to today if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / type
      Removed value: -"number"
  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. Changed3 schema fields changedv1.18.4
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Inclusive range end (YYYY-MM-DD or ISO 8601 datetime). Defaults to start_date if omitted — i.e. a single day. Set this explicitly whenever you want more than one day.",
+  "type": "string"
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Inclusive range start (YYYY-MM-DD or ISO 8601 datetime). Defaults to today if omitted.",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Kind of calendar item to return. Defaults to \"event\" if omitted.",
+  "enum": [
+    "event",
+    "assignment",
+    "sub_assignment"
+  ],
+  "type": "string"
+}
  4. First observedv1.18.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is to add context. It does: the unbounded/no-cap behavior is a genuinely useful trait beyond annotations, and the 'Canvas only returns type=event for today alone' note frames the default behavior. It stops short of noting pagination or return shape for an unbounded list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two tightly written sentences, front-loaded with purpose and the differentiator before the usage details. Every clause earns its place with no redundancy.

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 no output schema and annotations already carrying safety, the description is nearly complete: scope, defaults, ranges, and type switching are covered. It omits any mention of return volume or pagination for an explicitly 'unbounded' list, which an agent calling it might want.

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 baseline is 3, but the description adds real semantic value by explaining how parameters interact: end_date defaults to start_date (single day), so both must be passed for a range, and type switches between events and assignment due dates. This goes beyond the per-field schema text.

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+resource ('List calendar events for a course') and immediately distinguishes itself from the sibling list tools by scope. An agent can tell it apart from get_upcoming_events and get_my_upcoming_assignments without opening any 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?

Explicitly names the alternatives (get_upcoming_events, get_my_upcoming_assignments) and the condition that selects this tool over them (their ~1-week/20-item caps). It also gives positive invocation guidance: pass both start_date and end_date for a range and type="assignment" for due dates.

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