Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Calendar Events

list_calendar_events
Read-only

Retrieve a course's calendar events or assignment due dates across any date range, bypassing the one-week and 20-item limits of default Canvas endpoints.

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. 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"
  2. 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"
+}
  3. First observedv1.18.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only set readOnlyHint and openWorldHint, so the description is the main source for behavioral detail. It adds meaningful defaults and constraints: start_date defaults to today, end_date defaults to start_date, type defaults to 'event', and the tool is explicitly unbounded by the caps that other tools have. This is useful behavioral context beyond the annotations.

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?

The definition is two sentences with the core intent and differentiator front-loaded, followed by the parameter-usage detail. Every clause carries useful behavioral or routing information; no filler or repetition.

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?

For a 4-parameter read-only tool with 100% schema coverage, the description covers the main use case, the useful default behaviors, and the type switch. It doesn't address the 'sub_assignment' enum value or the output format, but those are not fatal gaps given the schema and the tool's read-only nature.

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. The description enriches the schema by explaining what the enum value 'assignment' produces (assignment due dates) and by clarifying the practical interaction between start_date and end_date to get a range rather than a single day. This is more than schema copy.

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 states a clear verb-resource pair ('List calendar events for a course') and distinguishes the tool from sibling tools by explicitly comparing it with get_upcoming_events and get_my_upcoming_assignments (unbounded vs. capped). It also explains the type variant for assignment due dates, giving an agent immediate differentiation without opening schemas.

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 names the two sibling tools and the selection criterion (unbounded vs. the ~1-week/20-item caps), so the agent knows when this tool is preferable. It also teaches the month-by-month date-range behavior and type switching. However, it never states directly when to fall back on the siblings, leaving the exclusion implicit.

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