Google_calendar

Gcal Create Event

gcal_create_event

Idempotent

Create a new calendar event with summary, start/end times, optional description, location, and attendee emails. Returns the created event ID.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	Yes	End time as RFC3339 timestamp or date for all-day events
`start`	Yes	Start time as RFC3339 timestamp (e.g., "2024-06-15T10:00:00-07:00") or date for all-day events ("2024-06-15")
`summary`	Yes	Title of the event
`location`	No	Location of the event
`attendees`	No	List of attendee email addresses
`time_zone`	No	Time zone (e.g., "America/Los_Angeles"). Defaults to calendar's time zone.
`calendar_id`	No	Calendar ID (default: "primary")
`description`	No	Description or notes for the event

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Created event ID
`end`	No	Event end time
`etag`	No	Event ETag
`kind`	No	Event resource kind
`error`	No	Error code if connection failed
`start`	No	Event start time
`status`	No	Event status
`created`	No	Creation timestamp
`message`	No	Error message if connection failed
`summary`	No	Event title
`updated`	No	Last update timestamp
`htmlLink`	No	HTML link to event
`location`	No	Event location
`attendees`	No	Event attendees
`description`	No	Event description

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attendees": {
+      "description": "Event attendees",
+      "items": {
+        "properties": {
+          "displayName": {
+            "description": "Attendee display name",
+            "type": "string"
+          },
+          "email": {
+            "description": "Attendee email",
+            "type": "string"
+          },
+          "responseStatus": {
+            "description": "RSVP status",
+            "enum": [
+              "needsAction",
+              "declined",
+              "tentative",
+              "accepted"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "created": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "description": {
+      "description": "Event description",
+      "type": "string"
+    },
+    "end": {
+      "description": "Event end time",
+      "properties": {
+        "date": {
+          "description": "Date for all-day events",
+          "type": "string"
+        },
+        "dateTime": {
+          "description": "DateTime for timed events",
+          "type": "string"
+        },
+        "timeZone": {
+          "description": "Time zone",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "etag": {
+      "description": "Event ETag",
+      "type": "string"
+    },
+    "htmlLink": {
+      "description": "HTML link to event",
+      "type": "string"
+    },
+    "id": {
+      "description": "Created event ID",
+      "type": "string"
+    },
+    "kind": {
+      "description": "Event resource kind",
+      "type": "string"
+    },
+    "location": {
+      "description": "Event location",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "start": {
+      "description": "Event start time",
+      "properties": {
+        "date": {
+          "description": "Date for all-day events",
+          "type": "string"
+        },
+        "dateTime": {
+          "description": "DateTime for timed events",
+          "type": "string"
+        },
+        "timeZone": {
+          "description": "Time zone",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "status": {
+      "description": "Event status",
+      "enum": [
+        "confirmed",
+        "tentative",
+        "cancelled"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "description": "Event title",
+      "type": "string"
+    },
+    "updated": {
+      "description": "Last update timestamp",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "end": "2024-06-15T10:30:00-07:00",
+    "start": "2024-06-15T10:00:00-07:00",
+    "summary": "Team Standup"
+  },
+  {
+    "attendees": [
+      "alice@example.com",
+      "bob@example.com"
+    ],
+    "description": "Initial planning meeting",
+    "end": "2024-06-20T15:30:00",
+    "location": "Conference Room A",
+    "start": "2024-06-20T14:00:00",
+    "summary": "Project Kickoff",
+    "time_zone": "America/New_York"
+  }
+]

First observedApr 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive, idempotent write operation. The description adds that the tool returns the created event ID, which is behaviorally relevant. No contradictions with annotations.

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, with no wasted words. The purpose is front-loaded, and all essential information is conveyed efficiently.

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 creation tool with an output schema (implied), the description appropriately mentions the returned event ID. It briefly covers parameters, though it omits mention of all-day events or timezone handling (covered by schema). Still largely complete.

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 coverage is 100%, so the schema already documents all 8 parameters. The description summarizes key parameters but does not add significant meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the action 'create' and the resource 'calendar event', listing key parameters (summary, start/end, optional fields). It distinguishes this tool from sibling tools like gcal_get_event and gcal_search_events by focusing on creation.

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?

The description does not explicitly state when to use this tool versus alternatives. While the purpose is clear, there is no guidance on prerequisites (e.g., calendar existence, attendee validity) or when not to use it.

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

All Google_calendar tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.