Skip to main content
Glama

Google_calendar

by io.github.pipeworx-io
OverviewAdmin

Gcal Get Event

gcal_get_event
Read-onlyIdempotent

Get full details of a specific event by ID (e.g., "event_12345"). Returns summary, description, times, attendees, location, and video conferencing links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesThe ID of the event to retrieve
calendar_idNoCalendar ID (default: "primary")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEvent ID
endNoEvent end time
etagNoEvent ETag
kindNoEvent resource kind
errorNoError code if connection failed
startNoEvent start time
statusNoEvent status
createdNoCreation timestamp
messageNoError message if connection failed
summaryNoEvent title
updatedNoLast update timestamp
htmlLinkNoHTML link to event
locationNoEvent location
attendeesNoEvent attendees
descriptionNoEvent description
conferenceDataNoVideo conferencing details

Schema Changelog

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

  1. Changed1 schema field changed
    • 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"
+    },
+    "conferenceData": {
+      "description": "Video conferencing details",
+      "properties": {
+        "entryPoints": {
+          "items": {
+            "properties": {
+              "entryPointType": {
+                "description": "Entry point type (e.g., video, phone)",
+                "type": "string"
+              },
+              "label": {
+                "description": "Entry point label",
+                "type": "string"
+              },
+              "uri": {
+                "description": "Entry point URI",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "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": "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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "event_id": "event_12345"
+  },
+  {
+    "calendar_id": "primary",
+    "event_id": "abc123def456"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds what fields are returned (summary, times, attendees, etc.), providing useful context beyond 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?

Single effective sentence followed by example, no wasted words, and front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations and output schema present, description provides sufficient context: it names return fields and gives usage example. No gaps.

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% with clear descriptions. The description adds no extra parameter details beyond examples, so baseline score 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 it retrieves full details of a specific event by ID, distinguishing it from listing or searching events among siblings.

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?

Implies use when event ID is known, but does not explicitly state when not to use or list alternatives, though inference from siblings is possible.

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

All Google_calendar toolsInspect
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.

Resources