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

icloud-calendar-mcp

by hrsather
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_event

Removes an event by UID from an iCloud calendar, deleting the entire series when the event recurs. Use it to clear outdated or canceled entries.

Instructions

Delete an event by UID. For a recurring event this deletes 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": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
calendarNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the most important behavioral trait: a recurring event's entire series is removed, which is a meaningful destructive side effect an agent must know before calling. It omits irreversibility/confirmation behavior, required auth scopes, and what happens to attendees or notifications.

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 short sentences, zero filler, and the destructive scope warning is placed immediately after the core action rather than buried. Every sentence earns its place.

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?

An output schema exists, so return values need not be explained, and the remaining gap set for a simple two-parameter delete is small. The series-deletion warning covers the highest-risk unknown, making the definition sufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across two parameters, so the description must compensate and largely does not. It restates that the uid is a UID but gives no format guidance (iCal UID vs internal ID), and the optional 'calendar' parameter with a null default is never mentioned at all.

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 names a specific verb and resource ('Delete an event') and pins the identifier ('by UID'), so it is instantly distinguishable from create_event/get_event/update_event/list_events by name alone. It stops short of explicitly routing against a sibling, but the scope statement about recurring series adds real specificity beyond the title.

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 only implied: an agent can infer you call this when you want an event removed, and the recurring-series note clarifies the blast radius of that call. There is no explicit when-to-use/when-not guidance, no mention of how to delete a single occurrence instead, and no prerequisites or permission notes.

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