icloud-calendar-mcp

Overview Schema Source Related Servers Discussions Admin

list_events

Retrieve calendar events between start and end dates, search all calendars or a specific one, and expand recurring events into individual occurrences.

Instructions

List events between start and end (ISO 8601 date or datetime; naive times use the server's default timezone). A date-only end is inclusive. Omit calendar (name or id) to search all calendars. Recurring events are expanded into individual occurrences, each with the series UID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "list_events"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes
`start`	Yes
`calendar`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and handles it well: it defines timezone handling for naive datetimes, states that a date-only `end` is inclusive, and warns that recurring events get expanded into individual occurrences carrying the series UID – a non-obvious behavior that would otherwise surprise a caller. It does not address volume/pagination behavior for large ranges across all calendars, which is the remaining behavioral gap.

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?

Four compact sentences, each carrying distinct information (range semantics, timezone rule, optional filter, recurrence expansion), with the core purpose front-loaded. No repetition of the tool name or filler.

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?

An output schema exists, so return values need not be described, and the recurrence-expansion note pre-empts the main confusion about result shape. The gap is scale handling – nothing says whether results are paged or capped when scanning all calendars over a wide range.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must document all three parameters, and it effectively does: `start`/`end` are ISO 8601 date-or-datetime with naive-time timezone fallback, `end` is inclusive when date-only, and `calendar` accepts a name or an id and is optional. This is meaning the bare schema cannot convey.

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 opens with a specific verb and resource plus a bounding scope: 'List events between start and end'. That separates it from the mutation siblings (create/update/delete_event) and from list_calendars, but it never explicitly contrasts itself with get_event, which is the closest ambiguous alternative.

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?

One real routing rule is given: 'Omit `calendar` (name or id) to search all calendars', which tells the agent how to broaden scope. Beyond that, there is no guidance on when to prefer this over get_event, or any exclusion such as the cost of wide date ranges across all calendars.

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

Deploy Server