Skip to main content
Glama
sfls1397

Apple Tools MCP

by sfls1397
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

calendar_add

Create calendar events with explicit local start/end times, recurrence rules (daily, weekly, monthly, yearly), and alerts. Returns the new event ID.

Instructions

Create a calendar event. Times must be explicit local datetimes (YYYY-MM-DD HH:MM). Supports recurrence (FREQ=DAILY/WEEKLY/MONTHLY/YEARLY with INTERVAL, COUNT or UNTIL, BYDAY) and alerts in minutes before the start. Returns the new event id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd as YYYY-MM-DD HH:MM local time (default: start + 1 hour)
countNoNumber of occurrences (1-1000); cannot be combined with until
notesNoEvent notes / description
startYesStart as YYYY-MM-DD HH:MM local time, or YYYY-MM-DD for all-day (required)
titleYesEvent title (required)
untilNoRepeat until this local datetime (YYYY-MM-DD HH:MM)
by_dayNoWeekly by-day list: MO TU WE TH FR SA SU
all_dayNoCreate an all-day event
confirmNoRequired for deletes and multi-recipient sends; without it the call only previews
dry_runNoPreview only: report what would happen and change nothing (default false)
intervalNoRecurrence interval, e.g. 2 for every other week (1-366)
locationNoEvent location
frequencyNoRecurrence frequency
recurrenceNoRaw RRULE instead of the structured fields, e.g. FREQ=WEEKLY;INTERVAL=1;COUNT=10
calendar_nameYesTarget calendar name from calendar_list_calendars (required)
alerts_minutes_beforeNoDisplay alerts in minutes before the start (max 5, up to 40320)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.8

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the required time format, recurrence capability, alert behavior, and that the new event id is returned, but says nothing about permissions, side effects, or how the confirm/dry_run preview behavior (documented only in the schema) interacts with creation.

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

Conciseness4/5

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

Four sentences, front-loaded with the core purpose, then format, then capabilities, then return value. Efficient and well-ordered, with no filler.

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 16-parameter create tool with no annotations and no output schema, the description covers the essentials: purpose, time format, recurrence, alerts, and the return value. The comprehensive schema supplies the rest, so the remaining gaps are minor.

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 100%, so the schema already documents all 16 parameters thoroughly, establishing a baseline of 3. The description reinforces the recurrence RRULE syntax and time format but adds little beyond what the schema fields already state.

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?

States a specific verb and resource ("Create a calendar event"), which cleanly separates it from the mutation siblings calendar_edit and calendar_remove. It doesn't explicitly name those alternatives, but the create semantics are unambiguous.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus calendar_edit, calendar_recurring, or calendar_remove, and offers no preconditions or exclusions. Usage must be inferred entirely from the name.

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