Skip to main content
Glama

List Calendar Events

list_events
Read-only

Lists calendar event resources and recurring series masters, excluding individual occurrences; expand recurrences with a calendar view query for date-range agendas.

Instructions

List calendar event resources (/me/events). Returns series masters for recurring meetings, NOT individual occurrences. For 'what's on my calendar between X and Y' use list_calendar_view instead — it expands recurrences into instances.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoNumber of events to return (default: 25)
filterNoOData filter expression
time_zoneNoShow times in this zone: an IANA name (America/New_York) or a Windows one (Eastern Standard Time). Default: UTC. Pass the user's own zone to read times as they would.
calendar_idNoID of the calendar to use, from list_calendars. Omit for your default calendar.
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds genuinely useful behavioral context about recurrence handling and the underlying endpoint. However, it says nothing about ordering, pagination behavior beyond the schema-documented fetch_all_pages flag, or what fields each returned event carries.

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?

Three short sentences, each earning its place: what it returns, what it does not return, and where to go instead. The most decision-relevant fact (series masters, not occurrences) is front-loaded.

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?

With no output schema, the description does the important work of characterizing the return shape (series masters for recurring meetings) and names the sibling that expands recurrences. Minor gaps remain around result ordering and default date window, but nothing that would cause a mis-call.

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%, so every parameter (top, filter, time_zone, calendar_id, fetch_all_pages) is already documented in the schema, including the guidance to pass the user's own time zone. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ('List calendar event resources (/me/events)') and immediately delimits what is returned: series masters, not individual occurrences. This distinguishes it cleanly from list_calendar_view without the agent needing to open either 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?

Gives an explicit routing rule with the user's own phrasing: 'For "what's on my calendar between X and Y" use list_calendar_view instead — it expands recurrences into instances.' It names the alternative and the condition that selects it.

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