Skip to main content
Glama

calendar_create_event

Create a new event in the connected calendar (Google, Outlook or a CalDAV calendar). Specify the title, start time, end time, and optionally invite attendees. Use ISO 8601 format for dates (e.g., 2024-12-15T14:00:00).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEvent end time in ISO 8601 format. If not provided, defaults to 1 hour after start. Also accepts 'end_time' as alias.
startNoEvent start time in ISO 8601 format (e.g., 2024-12-15T14:00:00). Also accepts 'start_time' as alias.
titleNoAlias for summary - event title.
summaryNoEvent title/summary. Required. Also accepts 'title' as alias.
end_timeNoAlias for end - event end time.
locationNoEvent location (physical address or virtual meeting link).
timezoneNoIANA timezone (e.g. 'Asia/Bishkek') that start/end WITHOUT an offset are in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone, which is what an event with no timezone gets.
attendeesNoList of attendee email addresses to invite.
account_idNoCalendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used.
start_timeNoAlias for start - event start time in ISO 8601 format.
calendar_idNoCalendar ID to create the event in. OMIT to use the agent's configured default calendar (or primary).
descriptionNoEvent description/notes.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
add_google_meetNoOld name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting.
conference_dataNoConference data for Google Meet. Alternative to add_google_meet flag.
zoom_account_idNoWith online_meeting_provider='zoom': which connected Zoom account hosts it. Only needed when the workspace has several.
add_online_meetingNoIf true, the event gets a video meeting link of its own: Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar. OMIT to skip the link.
send_notificationsNoWhether to email the attendees about the new event. true (default) sends the invitations; false saves the event silently. On Outlook calendars a silent save is refused when the event has guests.
online_meeting_providerNoWhich video meeting the event gets with add_online_meeting. 'default' (or OMIT): Google Meet on a Google calendar, Teams on Outlook. 'zoom': a Zoom meeting is created on the workspace's own connected Zoom account (refused when none is connected; no waiting room) and its join link is put in the event's location and description; add_online_meeting is not needed.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / online_meeting_provider
      Added value: +{
      +  "default": "default",
      +  "description": "Which video meeting the event gets with add_online_meeting. 'default' (or OMIT): Google Meet on a Google calendar, Teams on Outlook. 'zoom': a Zoom meeting is created on the workspace's own connected Zoom account (refused when none is connected; no waiting room) and its join link is put in the event's location and description; add_online_meeting is not needed.",
      +  "enum": [
      +    "default",
      +    "zoom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / zoom_account_id
      Added value: +{
      +  "description": "With online_meeting_provider='zoom': which connected Zoom account hosts it. Only needed when the workspace has several.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used."New value: +"Calendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used."
  3. Changed1 schema field changed
    • addedInput schema / properties / send_notifications
      Added value: +{
      +  "default": true,
      +  "description": "Whether to email the attendees about the new event. true (default) sends the invitations; false saves the event silently. On Outlook calendars a silent save is refused when the event has guests.",
      +  "type": "boolean"
      +}
  4. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / add_google_meet / description
      Previous value: -"If true, automatically creates a Google Meet link for the event. OMIT to skip Meet link."New value: +"Old name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting."
    • addedInput schema / properties / add_online_meeting
      Added value: +{
      +  "description": "If true, the event gets a video meeting link of its own: Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar. OMIT to skip the link.",
      +  "type": "boolean"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone for the event (e.g., 'America/New_York', 'UTC')."New value: +"IANA timezone (e.g. 'Asia/Bishkek') that start/end WITHOUT an offset are in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone, which is what an event with no timezone gets."
  6. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  7. Added
  8. Removed
  9. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID to create event in. Defaults to primary calendar."New value: +"Calendar ID to create the event in. OMIT to use the agent's configured default calendar (or primary)."
  10. First observed

TDQS

B3.3/5.0
Behavior3/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, non-idempotent, open-world mutation. The description adds provider support and date format but does not disclose important behavioral details such as default attendee notifications, silent-save restrictions on Outlook, or online meeting creation; those remain in the schema rather than the description.

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?

Three sentences, front-loaded with the core action, followed by the key fields and the ISO 8601 format example. There is no filler, and the structure makes the essential call shape immediately clear.

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 19-parameter create tool with no output schema, the description is quite minimal. The schema and annotations carry most of the burden, but the description does not address return behavior, default notification side effects, or account/calendar selection implications.

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 100%, so the schema already documents all 19 parameters including aliases, timezone semantics, account_id, send_notifications, and online meeting options. The description names only title, start, end, and attendees, adding essentially no parameter meaning beyond what the schema 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 states a specific verb and resource: "Create a new event in the connected calendar," and names supported calendar providers (Google, Outlook, CalDAV). It does not explicitly differentiate from siblings like calendar_update_event or calendar_delete_event, but "create a new event" is inherently distinct.

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?

The description implies use for creating a new event but gives no when-to-use versus when-not-to-use guidance, no prerequisites, and no mention of alternatives such as calendar_update_event. The ISO 8601 note is formatting guidance, not usage routing.

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.