Skip to main content
Glama

Put something on the calendar

create_calendar_event
Destructive

Puts an event on the calendar of address id. start and end are local wall times with no zone — 2026-11-03T14:00:00 — read in timezone, or the calendar’s default without one. For an all-day event end is the last day, inclusive. recurrence.rule is an RRULE such as FREQ=WEEKLY;BYDAY=TU. Attendees are not told unless send_invites is true, and then every attendee is emailed an invitation — that is mail to people outside the account, so only do it when you were asked to invite them. When retrying, reuse its idempotency_key.

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

Input Schema

NameRequiredDescriptionDefault
idYes
endYes
startYes
titleYes
statusNo
all_dayNo
locationNo
timezoneNo
attendeesNo
recurrenceNo
descriptionNo
send_invitesNo
idempotency_keyNoAny string unique to this send. Reuse the same key when retrying the same send, and it goes out once. Without one, an identical call within the hour counts as a retry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the external-mail side effect of send_invites is called out in bold, the timezone-free wall-time semantics are explained, and retry/idempotency behavior is described. This meaningfully extends the destructiveHint/openWorldHint annotations rather than repeating them.

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?

Dense and front-loaded: purpose first, then time semantics, then the side-effect warning, then retry advice. No filler sentences; every clause adds operative detail.

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 13-parameter mutation tool with no output schema, the description covers the non-obvious and dangerous parts (timezone, all-day, recurrence, invites, idempotency). Minor gaps remain for status/location/description fields, which are largely self-explanatory by name.

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?

With only 8% schema description coverage across 13 parameters, the description carries most of the burden and does so for the hardest ones: local wall times read in `timezone`, inclusive all-day `end`, and RRULE syntax for recurrence.rule. Parameters like status, location, and the attendee object shape are left undocumented, so it is not fully complete.

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 a specific verb and resource ('Puts an event on the calendar of address `id`') and is immediately distinguishable from the sibling update_calendar_event by name and semantics. The agent knows exactly what object is created and where.

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?

Explicit conditional guidance on the risky dimension: invites go out only when `send_invites` is true, and only when the user actually asked to invite people. Retry behavior is also spelled out (reuse the idempotency_key). It stops short of contrasting create vs update_calendar_event, but the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.