Skip to main content
Glama
epinethrone

icloud-mcp

by epinethrone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

calendar_delete_calendar

Destructive

Remove an entire calendar and every event in it; non-empty calendars require a preview and owner approval before deletion.

Instructions

Delete a whole calendar with every event in it; one that holds events needs a second call with a token from an owner-approved preview.

Use when: the owner explicitly asks to remove a calendar. Not for removing single events (use calendar_delete_event), for renaming (use calendar_update_calendar), or for keeping some events (move them out first with calendar_move_event). Parameters: calendar is a name (any case) or id from calendar_list_calendars. Omit confirm_token on the first call; pass the preview's token on the second. The token is bound to that calendar and its event count and expires after 10 minutes. Behavior:

  • An empty calendar is deleted at once.

  • One with events is left untouched by the first call, which returns a preview: show the owner the count and next events and call again only on their yes.

  • The default calendar (DEFAULT_CALENDAR, else 'Calendar' or 'Home') is refused; iCloud refuses shared or subscribed calendars.

  • The owner can restore a deleted calendar at iCloud.com (Settings, then Restore Calendars) for about 30 days; this server cannot. Returns: preview {deleted: false, calendar, events, next [{start, summary}], confirm_token, note}; done {deleted: true, calendar, events_deleted, note}. Errors:

  • "No calendar named '...'. Use one of: ..." for an unknown name or id: nothing is deleted; pick a listed name or check calendar_list_calendars.

  • A value that is one calendar's name and another's id is refused, not guessed: use the other calendar's name.

  • Token invalid, expired or stale because the event count changed: call again without it for a new preview.

  • Default calendar refused, or iCloud refused the delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarYesThe calendar to delete, by name.
confirm_tokenNoFrom the preview; needed when it holds events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "calendar_delete_calendarDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.11.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description goes well beyond: the confirm-token preview flow, 10-minute token expiry bound to calendar and event count, default-calendar refusal, iCloud shared/subscribed refusal, and the 30-day restore window at iCloud.com that this server cannot perform. This is exactly the extra context annotations can't convey.

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 the core action, then sectioned into Use when / Parameters / Behavior / Returns / Errors, so an agent can scan. It is long, but nearly every line is operational (refusals, token lifecycle, error strings) rather than padding; a slight trim of the Behavior bullets would not lose information.

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?

No output schema exists, yet the description documents both return shapes (preview vs done), the full error taxonomy with actionable recovery, and the irreversible-within-server nature of the delete. Nothing an agent needs to call this correctly or recover from failure is missing.

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 coverage is 100% so baseline would be 3, but the description adds real meaning: the name-vs-id ambiguity resolution, omitting confirm_token on the first call and passing the preview token on the second, and the token's binding/expiry semantics. That is beyond what the schema states.

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+resource ('Delete a whole calendar with every event in it') and immediately flags the two-step nature and the sibling tools it is not (calendar_delete_event, calendar_update_calendar, calendar_move_event). An agent can distinguish it from every calendar sibling without opening the 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?

Explicit 'Use when' clause (owner explicitly asks to remove a calendar) plus an explicit 'Not for' list naming three alternatives with the condition that selects each. Usage is fully determined.

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