Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Calendar Events

list_calendar_events
Read-onlyIdempotent

Lists calendar events or assignment due dates within a date range, defaulting to the next 14 days, and filters results to specific courses by ID.

Instructions

List calendar events, or assignment due dates with type=assignment, in a date range (default: the next 14 days). Read-only. Filter to specific courses with course_ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
typeNo"event" (default) for calendar events, or "assignment" for assignment due dates.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
end_dateNoEnd of the range, as an ISO 8601 date or date-time, e.g. "2026-11-30".
course_idsNoCourse IDs (numeric strings) to include. Get them from list_courses.
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed4 schema fields changedv1.1.3
    • addedInput schema / properties / course_ids / description
      Added value: +"Course IDs (numeric strings) to include. Get them from list_courses."
    • addedInput schema / properties / end_date / description
      Added value: +"End of the range, as an ISO 8601 date or date-time, e.g. \"2026-11-30\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • addedInput schema / properties / type / description
      Added value: +"\"event\" (default) for calendar events, or \"assignment\" for assignment due dates."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' is largely redundant confirmation rather than new disclosure. The genuinely additive behavior is the implied default date window, which is not stated in the schema. Nothing is said about pagination behavior despite a page parameter existing.

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 compact sentences with the resource and date-range scope front-loaded, followed by the assignment mode and the course filter. No filler or restated title text beyond a brief read-only note.

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 six-parameter, all-optional read tool with full schema coverage and annotations, this covers the essentials: default range, type switch, and course filtering. The remaining gap is pagination guidance (when to advance page, what limit defaults to), which an agent would have to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter documentation is already handled, establishing a baseline of 3. The description contributes the 14-day default window, which the schema does not state, but adds nothing about page/limit interaction or date format beyond what the schema documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (list calendar events) and clarifies the dual mode via 'assignment due dates with type=assignment'. It is clearly distinguishable from mutation siblings like update_calendar_event or delete_calendar_event. It stops short of explicitly contrasting with close read siblings such as list_upcoming_events or get_week_ahead, which share overlapping scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete default (next 14 days) and a narrowing recipe ('Filter to specific courses with course_ids'), which implies when the tool is useful. There is no explicit when-not guidance and no named alternative for adjacent needs like upcoming-event summaries or assignment lists.

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