Skip to main content
Glama
mathewcsims

mail-calendar-mcp

by mathewcsims

calendar_create_event

Create a new calendar event with start and end dates, summary, location, and recurrence options. The tool verifies the event exists after creation to confirm success.

Instructions

Create a new event. Verifies the event actually exists (by uid) after creation before reporting success — Calendar's scripting dictionary has known flaky spots for event creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesISO 8601 date/time.
summaryNo
locationNo
startDateYesISO 8601 date/time.
recurrenceNoRaw iCalendar RRULE-style text, e.g. 'FREQ=WEEKLY;INTERVAL=1;COUNT=5'. Editing recurrence on an already-recurring event is a known-flaky area — the tool verifies the change took effect and reports PLATFORM_LIMITATION if not.
alldayEventNo
descriptionNo
calendarNameNoCalendar name. Ambiguous if duplicated (common on multi-account setups) — use calendarIndex instead in that case.
calendarIndexNoPosition from calendar_list_calendars, for disambiguating duplicate calendar names. Stable only for the current Calendar.app process.
Behavior4/5

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

Description discloses verification after creation and known flaky spots, adding value beyond annotations (which only set readOnlyHint=false). No contradictions.

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 clear front-loading: purpose first, then crucial behavioral note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description is functional but minimal; lacks output details and comprehensive guidance for a 9-parameter tool. Schema partially compensates, but overall completeness is adequate.

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 coverage is 56% (below high threshold), and the description adds no parameter explanations. Relies heavily on schema, which has gaps (summary, location, alldayEvent, description undocmented).

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?

The description clearly states 'Create a new event', which is a specific verb+resource. It adds verification behavior, distinguishing it from siblings like calendar_update_event.

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?

No guidance on when to use this tool vs alternatives (e.g., calendar_update_event) or when not to use it. The description only implies use for creation.

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/mathewcsims/mail-calendar-mcp'

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