Skip to main content
Glama

Google_calendar

by io.github.pipeworx-io
OverviewAdmin

Gcal List Events

gcal_list_events
Read-onlyIdempotent

List calendar events with optional date filtering. Returns event summaries, start/end times, attendees, and locations. Use to view upcoming or past events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_byNoSort order (default: startTime). startTime requires singleEvents=true.
time_maxNoUpper bound (exclusive) for event end time as RFC3339 timestamp
time_minNoLower bound (inclusive) for event start time as RFC3339 timestamp (e.g., "2024-01-01T00:00:00Z")
calendar_idNoCalendar ID (default: "primary" for the user's main calendar)
max_resultsNoMaximum number of events to return (default 10, max 250)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
etagNoETag of the resource
kindNoResource kind identifier
errorNoError code if connection failed
itemsNoList of events
messageNoError message if connection failed
summaryNoCalendar summary/name
timeZoneNoCalendar time zone

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": {
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "etag": {
+      "description": "ETag of the resource",
+      "type": "string"
+    },
+    "items": {
+      "description": "List of events",
+      "items": {
+        "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"
+          },
+          "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"
+          },
+          "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"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "description": "Resource kind identifier",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    },
+    "summary": {
+      "description": "Calendar summary/name",
+      "type": "string"
+    },
+    "timeZone": {
+      "description": "Calendar time zone",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "calendar_id": "primary",
+    "max_results": 10,
+    "time_max": "2024-01-31T23:59:59Z",
+    "time_min": "2024-01-01T00:00:00Z"
+  },
+  {
+    "max_results": 25,
+    "time_min": "2024-06-15T09:00:00-07:00"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds value by specifying the return content (event summaries, start/end times, attendees, locations), which is not in 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?

The description is two sentences long, front-loaded with the core action ('List calendar events'), and every sentence provides essential information without redundancy.

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?

Given the presence of an output schema, the description adequately complements it by listing the key return fields. It does not cover ordering or pagination, which are in the schema, but overall provides sufficient context for a basic list tool.

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 fully documents parameters. The description mentions 'optional date filtering' which maps to time_min and time_max, but does not add new semantic detail beyond the schema. Baseline score of 3 is appropriate.

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 clearly states 'List calendar events' with optional date filtering, using a specific verb and resource. It distinguishes itself from sibling tools like gcal_create_event and gcal_search_events by focusing on listing, but does not explicitly name alternatives.

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 mentions 'Use to view upcoming or past events', providing some context for when to use the tool. However, it lacks explicit guidance on when not to use it or how it differs from gcal_search_events, which also lists events.

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