icloud-calendar-mcp

Overview Schema Source Related Servers Discussions Admin

create_event

Create iCloud Calendar events by calendar name or ID from a title and start time, with optional end, location, description, and recurrence for all-day or recurring events.

Instructions

Create an event in calendar (name or id). A date-only start makes an all-day event. end defaults to one hour (or one day) after start. rrule is an optional iCalendar recurrence rule such as FREQ=WEEKLY;COUNT=4. Naive times use the server's default timezone.

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": {
      "calendar": "<calendar>",
      "summary": "<summary>",
      "start": "<start>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No
`rrule`	No
`start`	Yes
`summary`	Yes
`calendar`	Yes
`location`	No
`description`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 15, 2026

TDQS

A4.4/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 disclose meaningful behavior: default `end` derivation, all-day semantics for date-only starts, and timezone handling for naive times. It omits side-effect details such as duplicate handling or required permissions, which keeps it short of a 5.

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?

Front-loaded with the core action, then each subsequent sentence delivers one concrete behavioral rule with no filler. Every clause earns its place.

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 semantically ambiguous parameters well and need not explain return values since an output schema exists. Minor gap: nothing is said about the required `summary` or about how conflicts/duplicates behave.

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 0%, so the description must compensate, and it does for the tricky parameters: `calendar` (name or id), `start` (date-only vs datetime), `end` (default), and `rrule` (iCalendar syntax with an example). `summary`, `location`, and `description` are left to their self-explanatory names.

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 and resource ('Create an event in `calendar`') and clarifies that `calendar` accepts a name or id. The create operation is unambiguously distinct from the delete/get/update/list siblings.

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?

Gives clear invocation context — date-only start yields an all-day event, end defaults to one hour (or one day), and naive times use the server's timezone. It does not name alternatives or exclusions, but for a create tool the operative guidance is how to shape inputs, which is well covered.

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

Deploy Server