Skip to main content
Glama

get_calendar_events

Fetch calendar events for the authenticated Canvas user to view upcoming deadlines, classes, and scheduled activities in one place.

Instructions

Get calendar events for the authenticated user

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": "get_calendar_events"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and says nothing beyond the one-line purpose. It does not disclose the time window covered (past only, upcoming only, or all), the result ordering, any result cap or pagination, or the response shape. 'Authenticated user' is the only behavioral hint, implying auth-scoping but not describing permission requirements.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity reflects under-specification rather than tight editing of a rich definition.

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

Completeness3/5

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

For a zero-parameter read tool with no output schema, an agent still needs to know what slice of the calendar comes back and roughly how much, and the description provides neither. The tool is simple enough that this is a moderate rather than fatal gap.

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?

The schema declares zero parameters at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the only missed opportunity is noting that the absence of parameters means no date-range or course filtering is possible.

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?

States a specific verb and resource (get calendar events) plus a scope qualifier ('for the authenticated user'), which is enough to distinguish it from data-shaped siblings like get_assignments or get_grades. It stops short of explicitly contrasting with the closest neighbors (get_todo_items, get_upcoming_assignments), which are the most likely confusion points.

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?

There is no guidance on when to call this rather than get_upcoming_assignments or get_todo_items, both of which can surface date-bearing items. No prerequisites, no exclusions, no statement of what the tool will not return (e.g. whether course-level events are included).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.