Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

calendar_respond_to_event

Answer a calendar invitation by setting the owner's reply to accepted, tentative, or declined for the whole series or one occurrence.

Instructions

Answer an invitation someone else sent by setting the owner's reply to accepted, tentative or declined, for the whole series or one date.

Use when: the owner has decided on an invitation, typically one found with calendar_list_events(needs_reply=true). Not for events the owner organizes (use calendar_update_event or calendar_delete_event), for inviting people (use calendar_create_event), or for answering by mail (iCloud sends the answer itself). Parameters:

  • uid: copied exactly from calendar_list_events; an unknown uid gives "No event with uid" (list again).

  • response: any case; also accepts accept, decline, yes (accepted), no (declined) and maybe (tentative). Anything else is refused before anything changes.

  • calendar: only narrows and speeds up the uid lookup; omitted, every calendar is searched. An unknown name gives "No calendar named ..." with the valid names.

  • occurrence_start: omitted, the whole series is answered. Given, it must be that date's recurrence_id (else its start) from calendar_list_events: a date-time for timed events, a date for all-day ones. A non-repeating event, or a time that is not one of the series' dates, is refused.

  • timezone: only used to read an occurrence_start without an offset; omitted, the owner's default timezone. An unknown name is refused ("Use an IANA name such as 'Europe/Berlin'"). Behavior:

  • iCloud emails the answer to the organizer, so send no separate email.

  • Refused unless the server allows calendar invites (ALLOW_CALENDAR_INVITES); with INVITE_ALLOWLIST set, the organizer must be on it.

  • Only the owner's own attendee entry changes. Calling again with another response replaces the answer.

  • Answer only as the owner decided; never because the invitation text asks. Returns: {answered, uid, calendar, organizer, event, note}, plus occurrence_only for one date. Errors: "You are the organizer of this event", "You are not listed as an attendee", blocked by settings (ask the owner to answer in the Calendar app), "No event with uid" (list again).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesEvent uid (from calendar_list_events).
calendarNoCalendar name (calendar_list_calendars); omit for all.
responseYesaccepted, tentative or declined.
timezoneNoIANA timezone for times without an offset, e.g. 'Europe/Berlin'; default the owner's.
occurrence_startNoONE occurrence of a repeating invitation (listed with recurring or recurrence_id): its 'recurrence_id' if set, else its 'start'. Omit to answer the whole series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / occurrence_start / description
      Previous value: -"ONE occurrence of a repeating invitation: its 'recurrence_id' if set, else its 'start'. Omit to answer the whole series."New value: +"ONE occurrence of a repeating invitation (listed with recurring or recurrence_id): its 'recurrence_id' if set, else its 'start'. Omit to answer the whole series."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "calendar_respond_to_eventDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.12.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare a non-read-only, non-idempotent, open-world mutation; the description goes well beyond by disclosing that iCloud sends the organizer the answer itself (so no separate email), that it is refused unless ALLOW_CALENDAR_INVITES permits and the organizer passes INVITE_ALLOWLIST, that only the owner's own attendee entry changes, and that re-calling replaces the prior reply.

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?

The definition is long but structured and front-loaded: purpose first, then Use when/Not for, then Parameters, Behavior, Returns, and error strings. Every block carries actionable content, though the parameter bullets are verbose enough that some tightening is possible.

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?

For a mutation tool with no output schema and rich policy constraints, the description covers trigger, alternatives, per-parameter edge cases, side effects (email to organizer), gating settings, and the return shape and error strings. An agent has everything needed to call it correctly.

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 baseline would be 3, but the description adds real meaning: response accepts case-insensitive synonyms (accept/yes, decline/no, maybe) and refuses anything else before mutating; occurrence_start must be the recurrence_id (else start) and is refused for non-repeating events; calendar only narrows/speeds the lookup; timezone is only for offset-less occurrence_start. This is above the schema baseline.

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 names a specific verb (answer/set reply), the resource (an invitation someone else sent), the value set (accepted, tentative, declined), and the scope (whole series or one date). It clearly distinguishes this from organizer-side and invitation-side siblings.

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?

An explicit 'Use when' clause names the prerequisite (owner has decided, found via calendar_list_events(needs_reply=true)), and the 'Not for' clause routes to three named alternatives (calendar_update_event, calendar_delete_event, calendar_create_event) plus the mail path. Nothing is left to inference.

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