Skip to main content
Glama
p-l-ta

calendar-mcp

by p-l-ta
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

create_event

Create new calendar events with support for recurrence, all-day, location, URL, and notes, syncing to all connected accounts via Calendar.app.

Instructions

Create a new event in Calendar.app. Goes through AppleScript so Calendar.app syncs the new event to all connected accounts. Returns the uid of the created event. Supports recurring events via the recurrence field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesISO 8601 end datetime, e.g. '2026-05-10T10:00:00'.
urlNoURL to attach to the event.
startYesISO 8601 start datetime, e.g. '2026-05-10T09:00:00'.
all_dayNoTrue for an all-day event. When true, start/end times are ignored — only the dates are used.
summaryYesEvent title.
calendarYesName of the target calendar (e.g. 'Calendar', 'Work'). Must match an existing calendar name exactly.
locationNoLocation string.
recurrenceNoRecurrence rule. Omit for a one-time event.
descriptionNoEvent notes/body.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / recurrence
      Added value: +{
+  "description": "Recurrence rule. Omit for a one-time event.",
+  "properties": {
+    "count": {
+      "description": "Stop after this many total occurrences (including the first). Mutually exclusive with end_date.",
+      "maximum": 9007199254740991,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "days_of_week": {
+      "description": "For weekly: which days to repeat on (e.g. ['MO','WE','FR'] for MWF). For monthly with week_of_month: the single day of the week (e.g. ['MO'] for 'first Monday').",
+      "items": {
+        "enum": [
+          "MO",
+          "TU",
+          "WE",
+          "TH",
+          "FR",
+          "SA",
+          "SU"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "end_date": {
+      "description": "Stop recurring on or before this date (ISO 8601). Mutually exclusive with count.",
+      "type": "string"
+    },
+    "frequency": {
+      "description": "How often the event repeats.",
+      "enum": [
+        "daily",
+        "weekly",
+        "monthly",
+        "yearly"
+      ],
+      "type": "string"
+    },
+    "interval": {
+      "default": 1,
+      "description": "Repeat every N frequency units. Default 1 (e.g. interval 2 with frequency 'weekly' = every other week).",
+      "maximum": 9007199254740991,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "week_of_month": {
+      "description": "For monthly recurrence by position: 1=first, 2=second, 3=third, 4=fourth, -1=last. Requires exactly one entry in days_of_week (e.g. week_of_month=1, days_of_week=['MO'] = first Monday of each month).",
+      "maximum": 5,
+      "minimum": -1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "frequency"
+  ],
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds valuable behavior beyond annotations: it goes through AppleScript, syncs to all connected accounts, returns the created event's uid, and supports recurrence. No contradiction with readOnlyHint=false or destructiveHint=false.

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 dense sentences with no filler, front-loaded with the core action and followed by mechanism, return value, and capability. Slight redundancy from repeating 'Calendar.app' twice, but overall well-structured.

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 9-parameter tool with a nested recurrence object and no output schema, the description supplies the key return value (uid) and the notable sync behavior. Error conditions and calendar prerequisites are left to the schema, but this is reasonably complete.

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 coverage is 100%, so all parameters are already documented. The description mentions the recurrence field, but that adds little beyond the detailed schema definition; baseline 3 is appropriate.

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 the exact action and target ('Create a new event in Calendar.app'), clearly distinguishing it from the sibling update/delete/read tools. Additional detail on the AppleScript mechanism and returned uid reinforces its identity as a creation tool.

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?

The verb 'Create' makes the primary use case clear, but the description does not explicitly contrast with update_event or mention prerequisites like existing calendars. Usage is implied rather than directly routed, so it sits at the middle of the scale.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/p-l-ta/calendar-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server