Skip to main content
Glama

Calendar: Create event

calendar_create_event
Destructive

Create an event in one resolved calendar. Require an explicit title, attendees array, start and end; preserve timezone and all-day semantics instead of guessing them.

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

Input Schema

NameRequiredDescriptionDefault
endYes
bodyNo
startYes
titleYes
notifyNoGoogle-only guest update policy; omit for Microsoft.
locationNo
timezoneNoIANA timezone for the event.
attendeesYes
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
conferenceNo
recurrenceNoRFC5545 RRULE, EXRULE, RDATE or EXDATE lines.
visibilityNo
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.
transparencyNo
background_colorNo
is_attendees_list_hiddenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / attendees / items / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, giving the agent the safety profile. The description adds useful input-handling behavior ('preserve timezone and all-day semantics instead of guessing them') and the requirement to supply explicit fields, but it never mentions the side effect that matters most for a create tool: attendees receive invitations, and the notify policy controls that.

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, both front-loaded and free of filler. The required-field constraint and the timezone/all-day warning each earn their place without restating the name.

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 16-parameter mutation with a nested oneOf schema and no output schema, the description covers the five required fields reasonably but omits the attendee-notification side effect, the Google-only nature of notify, and the account_id disambiguation flow. Annotations cover safety, but the operational behavior of creating an invitation-bearing event is only partially disclosed.

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 description coverage is 31% across 16 parameters, so the description must carry weight. It does add real meaning for title, attendees, start, and end, notably signalling that the start/end discriminated union encodes timezone and all-day semantics, but it says nothing about body, location, conference, recurrence, visibility, transparency, notify, or account_id selection, leaving most parameters undocumented by the prose.

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 uses a specific verb plus resource ('Create an event') and scopes it to 'one resolved calendar,' which cleanly separates it from calendar_update_event, calendar_delete_event, and calendar_cancel_event. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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?

'One resolved calendar' implies the calendar must first be identified via calendar_list_calendars, reinforcing the schema note about never passing a display name. However, there is no explicit guidance on when to use this versus calendar_update_event for an existing event, and no statement of prerequisites such as account selection.

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.