Skip to main content
Glama
iCloud Calendar MCP Server

iCloud Calendar MCP Server

by Glob0x17

update_event

Destructive

Modify an existing iCloud Calendar event to change its title, time, location, notes, calendar, reminders, or recurrence settings.

Instructions

Update an existing calendar event.

Before using this tool, make sure to:

  1. Ask the user which fields they want to update

  2. If moving to a different calendar, verify the calendar exists using calendars://list

  3. If updating time, confirm the new time with the user

  4. Ask if they want to add/update location if not specified

  5. Ask if they want to add/update notes if not specified

  6. Ask if they want to set reminders for the event

Args: event_id: Unique identifier of the event to update title: Optional new title start_time: Optional new start time in ISO format end_time: Optional new end time in ISO format notes: Optional new notes/description. Ask user if they want to update notes. location: Optional new location. Ask user if they want to specify/update location. calendar_name: Optional new calendar. Ask user which calendar to use, referencing calendars://list. all_day: Optional all-day flag reminder_offsets: List of minutes before the event to trigger reminders e.g. [60, 1440] means two reminders, the first 24 hours before the event and the second one hour before. recurrence_rule: Optional recurrence rule for the event. This should be an instance of RecurrenceRule with the following fields: - frequency: Frequency of the recurrence (e.g., DAILY, WEEKLY, MONTHLY, YEARLY). - interval: Interval between recurrences (e.g., every 2 weeks). - end_date: Optional end date for the recurrence. If specified, the recurrence will stop on this date. - occurrence_count: Optional number of occurrences. If specified, the recurrence will stop after this many occurrences. - days_of_week: Optional list of weekdays for the event. Use integers to represent days: - Sunday: 1 - Monday: 2 - Tuesday: 3 - Wednesday: 4 - Thursday: 5 - Friday: 6 - Saturday: 7

Note: Both end_date and occurrence_count should not be set simultaneously; choose one or the other, or leave both unset.

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": {
      "event_id": "<event_id>",
      "update_event_request": "<update_event_request>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
update_event_requestYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered; the description adds real behavioral context on top, namely that it is a partial update over an existing event and that calendar existence and time changes should be validated with the user first. It never explains the destructive consequences of the mutation itself (e.g. whether editing a recurring event reschedules all occurrences), which is the one gap left for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose line and numbered checklist are well front-loaded, but the Args section repeats the checklist verbatim ("Ask user if they want to update notes", "Ask user which calendar to use"), duplicating items 2, 4, and 5 without new information. The long recurrence enumeration is justified given the nested type, but the duplicated imperatives add bulk without adding meaning.

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 no explanation, and the description covers the workflow and the complex nested recurrence object adequately for a two-parameter tool. Completeness is undermined only by the schema drift on parameter names and the frequency enum representation, which could cause a caller to construct an invalid request.

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?

With 0% schema description coverage the description has to carry parameter meaning, and it largely does: ISO format for times, a worked example for reminder offsets ([60, 1440]), and a field-by-field breakdown of RecurrenceRule including the end_date/occurrence_count mutual exclusion. However, it names `reminder_offsets` while the schema property is `alarms_minutes_offsets`, describes `frequency` as DAILY/WEEKLY/MONTHLY/YEARLY strings while the schema defines an integer enum 0-3, and omits the schema's `url` property entirely, so an agent could easily send malformed values.

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 first sentence gives a specific verb and resource ("Update an existing calendar event"), which cleanly separates it from create_event, delete_event, list_events and list_calendars. It stops short of naming a sibling or stating what makes it distinct from, say, create_event when an event might not yet exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The numbered pre-flight list gives concrete when-to-use behavior: collect the desired fields from the user, verify a target calendar exists, confirm time changes. It lacks any when-NOT-to-use guidance (e.g. recurring-event scope, or preferring create_event when the event is missing) and it points at a `calendars://list` resource rather than the available `list_calendars` sibling, which is a minor routing ambiguity.

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