Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Create calendar event

create_calendar_event

Create and schedule calendar events or meetings for the authenticated user, invite attendees with iMIP notifications, and set recurrence, reminders, or all-day personal time blocks.

Instructions

Create, schedule or book a new calendar event or meeting on the user’s calendar, and invite people to it with the authenticated user as organizer. Attendees receive iMIP invitations (pass notify: "none" to suppress them); omit attendees for a personal event — a block of the user’s own time. For an all-day event (a day off, a vacation) pass start/end as dates. Pass recurrence for a repeating series (e.g. a weekly team meeting) in one call, and reminderMinutesBefore to be reminded. Defaults to the user’s default calendar.

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": {
      "end": "<end>",
      "start": "<start>",
      "title": "<title>"
    },
    "name": "create_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEvent end as ISO 8601 (see `timeZone`). For an all-day event a date, exclusive: the day after the last day (a day off on 2026-10-03 ends 2026-10-04).
startYesEvent start as ISO 8601 (see `timeZone`), or a date (2026-10-03) for an all-day event.
titleYes
notifyNoWhether to send the iMIP invitations. `all` (default) sends them; `none` invites nobody.
showAsNoWhether this event counts as busy time. `busy` (default) means it does; `free` means it does not — for holds, reminders and travel buffers the user does not want counted against their availability. Inviting people makes an event count as busy time, so `free` is refused when `attendees` are given.
locationNo
timeZoneNoIANA zone for start/end, e.g. Europe/Berlin: their clock digits are read as wall-clock time here, overriding any offset. Defaults to the account timezone, then UTC.
attendeesNoEmail addresses to invite; each receives an iMIP invitation. Omit for a personal event — a block of the user’s own time — with no invitations sent.
recurrenceNoRepeat rule; omit for a one-off event. start/end are its first occurrence. Either a raw RFC 5545 RRULE ("FREQ=WEEKLY;BYDAY=TH", "FREQ=DAILY;COUNT=10") or {frequency, interval?, byDay?, until?|count?}. Use at most one of until/count; The object’s `until` is ISO (2026-12-31 or 2026-12-31T00:00:00Z); a raw UNTIL is compact (20261231 or 20261231T000000Z). Either is converted to match the event (a date on an all-day series). A raw rule is only lightly validated, so a malformed one fails later at the server.
calendarUrlNo
descriptionNo
reminderMinutesBeforeNoRemind the user this many minutes before the start (e.g. 30); omit for no reminder. An all-day event starts at 00:00, so 900 = 09:00 the day before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses important side effects: the user is organizer, attendees receive iMIP invitations, notify none suppresses them, and omitted attendees creates a personal time block. It also states the default calendar behavior. It leaves out auth requirements, duplicate-event behavior, and rate limits, but the annotations already cover non-idempotence.

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?

The description is front-loaded with the core purpose and then covers the main usage scenarios in dense but efficient prose. Every clause contributes practical guidance, and there is no obvious 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 12-parameter creation tool with no output schema, the description covers the most important behavioral scenarios and defaults. It does not mention return value or some notable parameters and constraints, but the schema fills many of those gaps.

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?

The schema already describes most key parameters at moderate-to-high detail, and the description largely restates those meanings for notify, attendees, all-day start/end, recurrence, and reminderMinutesBefore. It adds some value by mentioning default calendar behavior and organizer identity, but several parameters such as showAs, timeZone, location, calendarUrl, and description receive no additional clarification.

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 uses a specific verb set ("Create, schedule or book") and a precise resource ("new calendar event or meeting") with scope ("on the user’s calendar"). This clearly separates creation from sibling operations like update_calendar_event and delete_calendar_event.

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?

It gives clear contextual guidance: omit attendees for a personal block, pass dates for an all-day event, use recurrence for repeating series, and notify none to suppress invitations. It does not explicitly compare against siblings such as update_calendar_event, but the creation context is clear.

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