mcp-server-google-workspace

calendar_list_events

List calendar events from any accessible Google Calendar within a date range, returning times with timezone information.

Instructions

List calendar events for a specific date range. Can list events from any accessible calendar. Returns event times with their timezone information.

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": "calendar_list_events"
  }
}

Input Schema

Name	Required	Description	Default
`calendarId`	No	Calendar ID (default: "primary" for your main calendar). Use calendar_list_calendars to get IDs of shared calendars.	primary
`date`	No	Start date in YYYY-MM-DD format (default: today)
`days`	No	Number of days from start date (default: 1)
`maxResults`	No	Maximum number of events (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jun 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description bears the full burden of behavioral disclosure. It adds that the tool 'can list events from any accessible calendar' and 'returns event times with their timezone information', but it omits details on pagination, ordering, returned fields beyond times, and behavior on invalid inputs.

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 purpose, and contains no redundant information. Every sentence earns its place.

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

Completeness3/5

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

Given no output schema, the should mention return value details. It partially does by noting timezone information but does not specify the full return structure (e.g., event fields, ordering, pagination). This leaves gaps for an agent.

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?

All 4 parameters have schema descriptions at 100% coverage. The description adds 'date range' context but does not provide additional meaning beyond what the schema already offers, so baseline 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 the verb 'list', the resource 'calendar events', and the scope 'for a specific date range' and 'any accessible calendar'. It effectively distinguishes itself from siblings like calendar_create_event (create) and calendar_list_calendars (list calendars).

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 description provides no explicit guidance on when to use this tool versus its siblings or alternatives. It does not mention when not to use it or compare it to other tools, leaving the agent to infer usage context.

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

Deploy Server