Skip to main content
Glama

create_event

Schedule calendar events with ISO 8601 dates, optional all-day settings, alerts, repeats, location, notes, and URL, so you can add structured entries to Apple Calendar.

Instructions

Create an event. Dates are ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. With date-only 'start' and 'end', or 'all_day' true, it is an all-day event and 'end' is the last day. 'alerts' and 'repeat' are optional.

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

Input Schema

NameRequiredDescriptionDefault
endYesEnd, after 'start'. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
urlNoA URL, for example https://example.com.
notesNoNotes.
startYesStart. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
titleYesEvent title.
alertsNoMinutes before the start, 0 to 40320, at most 5. For example [10, 1440] is an alert 10 minutes before and one day before.
repeatNoHow the event repeats. Set 'frequency'. 'interval' (1 to 99, default 1) is the gap between repeats. Give 'end' (a date, the last day a repeat can start) or 'count' (1 to 999 occurrences), not both. Without them the event repeats forever. 'days' is only for 'weekly'. Frequency 'none' or null removes the rule.
all_dayNoAll-day event.
calendarNoCalendar name or id. Default: the default calendar.
locationNoLocation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the description isn't carrying the full safety burden. It adds genuinely useful behavior that the schema does not: date-only start/end or all_day true produces an all-day event, and in that case 'end' is the inclusive last day. It does not mention duplicate handling, side effects, or notification behavior.

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 short sentences, front-loaded with purpose, then the format rule, then the all-day rule, then optionality. The repeated ISO 8601 examples echo the schema and are the only real waste.

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?

For a 10-parameter tool with a nested repeat object and no output schema, the description covers creation semantics and all-day behavior well but says nothing about the return value (e.g., the created event's id) or default calendar side effects. Adequate, with a clear gap on response shape.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: how start, end, and all_day interact to determine event type, and that alerts/repeat are optional. The ISO 8601 examples duplicate what the schema already provides.

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?

The description opens with a specific verb+resource ('Create an event'), which is unambiguous against siblings like update_event, delete_event, or get_event. It does not explicitly name or contrast those alternatives, so it stops short of full sibling differentiation.

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?

Usage is only implied: an agent infers this is for new events rather than modifying existing ones. The description does give usable conditional guidance for the all-day case (date-only values or all_day true) but never states when to prefer create_event over update_event or how it relates to calendars.

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