Skip to main content
Glama
redpop

apple-calendar-mcp

by redpop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_event

Add a new event to Apple Calendar, choosing a specific calendar or the default. Supports all-day events, alarms, notes, location, and meeting links.

Instructions

Creates a new event. Without calendarId the default calendar is used. Read-only calendars are rejected. For all-day events, alarms are floored to whole days and placed at 09:00, matching Calendar.app. Never modifies or deletes existing events — neither is currently possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd, ISO 8601 with offset. For all-day events (allDay: true) both common conventions are accepted and normalised to the same day: the last day included (…T23:59:59) or midnight of the following day (…T00:00:00 of the next date).
urlNoAssociated URL, for example a meeting link
notesNoFree-text note attached to the event
startYesStart, ISO 8601 with offset
titleYesTitle of the event
allDayNoAll-day event. When true, only the calendar days of start and end are used.
locationNoLocation, as shown in Calendar.app
calendarIdNoCalendar to create the event in. Defaults to the system default calendar.
alarmMinutesBeforeNoAlarms in minutes before the start. For all-day events these are floored to whole days and placed at 09:00, matching Calendar.app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate it is not read-only and not destructive, but the description adds valuable context: read-only calendar rejection, all-day alarm flooring to 09:00, and the explicit note that existing events are never modified or deleted. These are behaviors beyond what annotations convey, giving the agent a strong understanding of side effects and constraints.

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 sentences with no fluff. The main purpose is stated first, followed by essential caveats. Every sentence carries useful information, and the structure is clean and front-loaded.

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 tool with 9 parameters and no output schema, the description covers the most critical behaviors (default calendar, read-only rejection, alarm handling, and non-destructiveness). It does not mention the return value, but for a create operation the agent can reasonably infer the created event is returned. Overall, it provides sufficient context for correct invocation.

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?

The schema covers all parameters (100%), so baseline is 3. The description adds meaning for calendarId (default behavior) and alarmMinutesBefore (all-day flooring), which are not fully explained in the schema. It does not add semantics for every parameter, but the key ones are clarified, exceeding the baseline.

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?

Clearly states it creates a new event and describes the primary behavior (default calendar, read-only rejection). The statement 'Never modifies or deletes existing events' explicitly differentiates it from update_event and delete_event, making its purpose unmistakable even without naming 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?

Provides context on when to use it: default calendar behavior and the rejection of read-only calendars. It implicitly contrasts with update/delete via the 'never modifies or deletes' clause, but does not explicitly name alternatives or give conditions like 'use list_calendars to find a calendarId.' Still, the guidance is clear enough for most cases.

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

Install Server

Other Tools