Skip to main content
Glama
Sign In
icloud-calendar-mcp

icloud-calendar-mcp

by hrsather
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_event

Modify an iCloud Calendar event by UID: change selected fields, leave omitted fields unchanged, clear location/description, preserve duration when only start changes, or update a recurring series.

Instructions

Update fields of an event by UID; omitted fields are unchanged and an empty string clears location or description. Changing only start keeps the event's duration. For a recurring event this changes the whole series.

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

Input Schema

NameRequiredDescriptionDefault
endNo
uidYes
startNo
summaryNo
calendarNo
locationNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses partial-update semantics (omitted fields unchanged), the empty-string clearing convention for location/description, duration preservation when only start changes, and the high-impact side effect that a recurring event's entire series is modified. It omits permission/auth requirements and whether the change is reversible or recoverable.

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?

Two compact sentences, front-loaded with the verb and key, with every clause carrying non-obvious semantics. No filler or restatement of the name.

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?

For a 7-parameter mutation tool with no annotations, the description covers the riskiest behaviors (partial update, clearing, series-wide change), and an output schema exists so return values need not be described. The main gap is the unexplained calendar parameter and any error/permission behavior.

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

Parameters3/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate and only partly does: it explains uid, the null/omitted behavior for the nullable fields, empty-string semantics for location and description, and start's duration-preserving behavior. The 'calendar' parameter is completely unexplained (does it move the event between calendars?), as are summary and end.

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 gives a specific verb and resource ('Update fields of an event') plus the addressing key ('by UID'), which is enough for an agent to separate it from create_event, delete_event, and get_event. It does not explicitly name siblings, so it falls short of a 5.

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?

Usage is implied by the update semantics and by the note that this changes whole series for recurring events, but there is no explicit 'use this when' statement or named alternative. An agent can infer when to call it, yet nothing steers it away from misuse on recurring events.

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