Skip to main content
Glama

List events

list_events
Read-only

List calendar events that overlap a time range, including recurring occurrences, sorted by start time; defaults to the next seven days.

Instructions

List calendar events (recurring events are expanded into occurrences) that overlap a time range, sorted by start. Defaults to the next 7 days from today (UTC). Returned times are UTC.

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
endNoRange end (default: start + 7 days)
limitNoMaximum events (default 100)
startNoRange start (ISO 8601; without an offset it is UTC unless timeZone is given)
calendarNoCalendar (default: the main calendar). Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders
timeZoneNoIANA time zone for start/end without an offset, e.g. "Europe/London"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: recurring events are expanded into individual occurrences, results are sorted by start time, the default window is the next 7 days, and returned times are UTC — all of which affect how an agent interprets results.

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 clauses, zero filler, and the core semantics (overlap range, recurrence expansion, sort order) are front-loaded before the defaults. Every sentence carries information an agent needs.

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 read-only list tool with full schema coverage and no output schema, the definition covers the essentials: what is listed, how recurrences behave, ordering, defaults, and timezone handling. Pagination behavior beyond the limit parameter is not described, which is the only notable 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?

Schema coverage is 100%, so the baseline would be 3. The description adds meaning beyond the schema by defining the default range (next 7 days from today) and stating that returned times are UTC, clarifying the UTC-vs-offset semantics that the start/end/timeZone parameters hinge on. It says nothing about limit or calendar, which the schema already covers.

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 gives a specific verb and resource ("List calendar events") plus the qualifying scope: events overlapping a time range, with recurring events expanded into occurrences and results sorted by start. That is enough to distinguish it from get_event (single event) and list_calendars (calendars, not events), though no sibling is named outright.

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?

Usage is implied rather than stated: an agent can infer this is the way to enumerate events in a window, and the default of the next 7 days is a useful context cue. However, there is no explicit when-to-use vs get_event or list_calendars guidance, and no stated exclusions.

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