Skip to main content
Glama
Sign In
google-services-mcp

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List calendar events

google_calendar_list_events

List upcoming Google Calendar events and filter them by time range or search query. Use it to retrieve scheduled meetings, appointments, or agenda items for a chosen calendar and account.

Instructions

List upcoming events in a calendar, optionally filtered by time range or query.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search (e.g. meeting).
accountNoAccount nickname to use.
timeMaxNoEnd of range (ISO 8601).
timeMinNoStart of range (ISO 8601, default now).
pageTokenNoPage token from a previous result's nextPageToken. Continues that query; omit to start a new one.
calendarIdNoCalendar ID (default primary).
maxResultsNoMax events (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.97
    • changedInput schema / properties / pageToken / description
      Previous value: -"Page token from a previous result's nextPageToken."New value: +"Page token from a previous result's nextPageToken. Continues that query; omit to start a new one."
    • addedInput schema / properties / pageToken / minLength
      Added value: +1
  2. Changed1 schema field changedv0.1.95
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Page token from a previous result's nextPageToken.",
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.30
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. 'List' implies a safe read and 'upcoming' discloses the default forward-looking scope, which is useful. However, it omits permissions/account requirements, result ordering, pagination behavior, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero wasted words, and the filtering caveat is placed correctly after the core action. It is efficient, though arguably thin rather than optimally sized.

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

Completeness2/5

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

For a 7-parameter tool with no annotations and no output schema, the description leaves the agent without return-shape or pagination context and gives no guidance on calendar/account selection. The fully documented schema compensates for parameter gaps, but behavioral gaps remain.

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 every parameter (q, account, timeMin/timeMax, pageToken, calendarId, maxResults) is already documented in the schema. The description's mention of 'time range or query' adds only marginal framing, so the baseline 3 applies.

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?

States a specific verb and resource ('List upcoming events in a calendar') with scope qualifiers (time range, query). It does not differentiate itself from siblings like google_calendar_free_busy or google_calendar_get_event, so it falls short of a 5.

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 phrase 'optionally filtered by time range or query' hints at capabilities but never says when to prefer this over google_calendar_free_busy, google_calendar_get_event, or google_calendar_list_calendars. There are no exclusions, prerequisites, or alternative routing cues.

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

Deploy Server

Other Tools