Skip to main content
Glama

Google_calendar

by io.github.pipeworx-io
OverviewAdmin

Gcal Search Events

gcal_search_events
Read-onlyIdempotent

Search events by keyword across summaries, descriptions, locations, and attendees. Returns matching event details and times. Use to find events by topic or participant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text search query to match against event fields
time_maxNoUpper bound for event end time as RFC3339 timestamp
time_minNoLower bound for event start time as RFC3339 timestamp
calendar_idNoCalendar ID (default: "primary")
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
itemsNoMatching 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": "Matching 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: +[
+  {
+    "query": "budget review"
+  },
+  {
+    "calendar_id": "primary",
+    "max_results": 20,
+    "query": "client meeting",
+    "time_max": "2024-06-30T23:59:59Z",
+    "time_min": "2024-06-01T00:00:00Z"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the tool as read-only and idempotent. The description adds that it returns 'matching event details and times' but does not cover pagination behavior or rate limits, which are standard for search APIs.

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 concise sentences that front-load the core purpose and use case. No extraneous information.

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 100% schema coverage, existing annotations, and an output schema (implied), the description provides sufficient context for a search tool. It could mention that search is across all specified fields, but the current level is adequate.

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 baseline is 3. The description does not add further detail beyond the schema, as it only mentions the 'query' capability without elaborating on time bounds, calendar_id, or max_results.

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 tool searches events by keyword across multiple fields (summaries, descriptions, locations, attendees) and returns details/times. This distinguishes it from siblings like gcal_list_events which filter by time or calendar.

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?

The description gives a clear use case ('find events by topic or participant') but does not explicitly contrast with alternatives like gcal_list_events or gcal_get_event for when not to use this tool.

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