Skip to main content
Glama

gcal_list_events

List events from a connected Google Calendar in start-time order to review schedules, find upcoming occurrences, and check availability.

Instructions

(Beta) List events of a Google Calendar of a connected Google account, in start order, each occurrence of a...

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gcal_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses ordering and per-occurrence expansion of recurring events plus a Beta status, but says nothing about the default calendar/account used, the default time window, pagination or result limits, or whether the call is read-only.

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

Conciseness3/5

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

The key facts (list, start order, occurrences, beta) are front-loaded, but the text ends mid-sentence ('each occurrence of a...'), so the definition is truncated rather than tight. Size is small; completeness of the sentence is the problem.

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 zero-parameter, no-output-schema list tool, the description must explain default scope: which calendar, which time range, how many results and whether paging is needed. It covers none of these and is truncated, leaving the agent unable to predict what comes back.

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?

The schema has zero parameters, which normally yields a baseline 4, but the description implies selectors ('a Google Calendar', 'a connected Google account') that the schema offers no way to supply. The reader is left not knowing which calendar or account is actually listed, so a small deduction below baseline is warranted.

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 events of a Google Calendar of a connected Google account') and adds ordering ('in start order') plus recurring-event expansion ('each occurrence'). That is enough to separate it from gcal_list_calendars or gcal_create_event, though the sentence is cut off so the full scope is never stated.

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?

There is no when-to-use guidance and no named alternative, even though siblings like m365_list_events, outlook_calendar_list_events and list_calendar_events exist. Nothing tells the agent when this Google-specific tool is preferred over those.

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