Skip to main content
Glama

Read calendar events

events_list
Read-onlyIdempotent

Lists flat calendar events, optionally within a time window, ordered by start, so you can see what is planned or find an event ID.

Instructions

List the flat calendar events, optionally inside a time window, ordered by start. Use it to see what is planned or to find an event id; use event_get when you already have the id, and calendar_subscription_get for the feed URL that adds the calendar to a calendar app. A recurring event comes back once with its recurrence rule, not expanded into single dates. Send from and to together to limit the window; without them all events are returned. More than 1000 matches fail with 503 events_window_too_large, so narrow the window. Each event has id, title, description, startsAt, endsAt, allDay, location, recurrence, createdByMemberId and updatedAt.

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

Input Schema

NameRequiredDescriptionDefault
toNoWindow end: a date or an ISO 8601 datetime with offset. A bare date covers that whole day (sent as 23:59:59.999 UTC).
fromNoWindow start: a date (2026-12-01) or an ISO 8601 datetime with offset.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / from / description
      Previous value: -"Window start: a date (2026-12-01) or an ISO 8601 datetime with offset. Only applies together with to."New value: +"Window start: a date (2026-12-01) or an ISO 8601 datetime with offset."
    • changedInput schema / properties / to / description
      Previous value: -"Window end: a date or an ISO 8601 datetime with offset. A bare date covers that whole day (sent as 23:59:59.999 UTC). Only applies together with from."New value: +"Window end: a date or an ISO 8601 datetime with offset. A bare date covers that whole day (sent as 23:59:59.999 UTC)."
  2. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / from / description
      Added value: +"Window start: a date (2026-12-01) or an ISO 8601 datetime with offset. Only applies together with to."
    • addedInput schema / properties / to / description
      Added value: +"Window end: a date or an ISO 8601 datetime with offset. A bare date covers that whole day (sent as 23:59:59.999 UTC). Only applies together with from."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent and non-destructive, and the description still adds real behavior: recurring events return once with their recurrence rule rather than expanded, results are ordered by start, and over 1000 matches fail with 503 events_window_too_large. The list of returned fields compensates for the missing output schema.

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?

Front-loaded with purpose and routing, then constraints, then shape of the result — a logical order with no filler sentences. It is on the long side, and the trailing field enumeration reads as a list, but every element carries information an agent needs.

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

Completeness5/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 supplies the event field set, the recurrence non-expansion rule, ordering, and the failure threshold that forces windowing. For a three-optional-parameter list tool with full schema coverage, nothing needed for a correct call is missing.

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 is 3, but the description adds a cross-parameter rule the schema does not express: 'Send from and to together to limit the window; without them all events are returned.' The wgCode parameter is not discussed in the description, so it stops short of a 5.

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?

The opening sentence gives a specific verb and resource ('List the flat calendar events'), plus scope ('optionally inside a time window, ordered by start'). It explicitly separates itself from event_get ('when you already have the id') and calendar_subscription_get, so an agent can choose without opening a 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?

States the two concrete use cases ('see what is planned', 'find an event id') and names the alternative for each competing need: event_get for a known id, calendar_subscription_get for the feed URL. Nothing is left to inference about when this tool is the wrong pick.

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