Skip to main content
Glama

canvas_list_calendar_events

Retrieve calendar events from the Canvas LMS within a specified date range to organize and manage schedules effectively. Input start and end dates in ISO format for streamlined event tracking.

Instructions

List calendar events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoEnd date (ISO format)
start_dateNoStart date (ISO format)

Implementation Reference

  • Core handler implementation: Fetches calendar events from Canvas API endpoint '/calendar_events' with optional date range parameters.
    async listCalendarEvents(startDate?: string, endDate?: string): Promise<CanvasCalendarEvent[]> {
      const params: any = {
        type: 'event',
        all_events: true
      };
      
      if (startDate) params.start_date = startDate;
      if (endDate) params.end_date = endDate;
    
      const response = await this.client.get('/calendar_events', { params });
      return response.data;
    }
  • src/index.ts:345-355 (registration)
    Tool registration in TOOLS array, including name, description, and input schema.
      name: "canvas_list_calendar_events",
      description: "List calendar events",
      inputSchema: {
        type: "object",
        properties: {
          start_date: { type: "string", description: "Start date (ISO format)" },
          end_date: { type: "string", description: "End date (ISO format)" }
        },
        required: []
      }
    },
  • MCP server handler dispatch: Calls CanvasClient.listCalendarEvents and formats response.
    case "canvas_list_calendar_events": {
      const { start_date, end_date } = args as { start_date?: string; end_date?: string };
      const events = await this.client.listCalendarEvents(start_date, end_date);
      return {
        content: [{ type: "text", text: JSON.stringify(events, null, 2) }]
      };
    }
  • TypeScript interface defining the structure of Canvas calendar events (output schema).
    export interface CanvasCalendarEvent {
      id: number;
      title: string;
      start_at: string;
      end_at: string;
      description: string;
      location_name?: string;
      location_address?: string;
      context_type: 'Course' | 'User' | 'Group';
      context_id: number;
      workflow_state: 'active' | 'deleted';
      hidden: boolean;
      url?: string;
      html_url: string;
      all_day: boolean;
      assignment?: CanvasAssignment;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List calendar events' implies a read-only operation, but it doesn't specify permissions required, pagination behavior, rate limits, or what happens if dates are omitted (since parameters are optional). This is a significant gap for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is a single, efficient sentence with zero waste. It's front-loaded and to the point, though it could be more informative without sacrificing conciseness (e.g., by adding minimal context like 'for a course').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain the return format (e.g., list of events with details), error conditions, or behavioral traits like pagination. For a list tool with optional date parameters, this leaves critical gaps for an agent to use it effectively.

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 description coverage is 100%, with clear descriptions for 'start_date' and 'end_date' as ISO format strings. The description adds no parameter semantics beyond what the schema provides, but since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description 'List calendar events' clearly states the verb ('list') and resource ('calendar events'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'canvas_list_assignments' or 'canvas_list_announcements' beyond the resource type, and it lacks specificity about scope or context (e.g., whose calendar, what kind of events).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a course context), exclusions, or comparisons to other list tools (e.g., 'canvas_list_assignments' for assignments vs. this for calendar events), leaving the agent to infer usage from the name alone.

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

Related 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/DMontgomery40/mcp-canvas-lms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server