mcp-server-google-workspace

calendar_list_calendars

Retrieve a list of all accessible Google calendars, including shared ones, with optional filters for hidden calendars and minimum access role. Use this to obtain calendar IDs for subsequent operations.

Instructions

List all accessible calendars including shared calendars. Use this to get calendar IDs for other calendar operations.

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_calendars"
  }
}

Input Schema

Name	Required	Description	Default
`showHidden`	No	Include hidden calendars (default: false)
`minAccessRole`	No	Minimum access role filter (freeBusyReader, reader, writer, owner)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jun 9, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It only mentions that the tool lists 'accessible calendars including shared calendars,' which implies a read operation. However, it does not disclose any behavioral traits like permissions required, pagination, or rate limits.

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, front-loading the purpose and usage intention. Every sentence adds value with no wasted words.

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?

The tool has no output schema, but the description gives a clear idea of what the tool returns (a list of calendars with IDs). It could be more complete by mentioning typical fields in the response, but the current description is mostly sufficient for a straightforward 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 description coverage is 100%, so the parameters are already well-documented in the schema. The description does not add additional meaning beyond what the schema provides.

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 action 'list all accessible calendars including shared calendars' and specifies the use case: 'get calendar IDs for other calendar operations.' This distinguishes it from sibling tools like calendar_list_events.

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 explicitly states when to use the tool ('to get calendar IDs for other calendar operations'), but does not mention scenarios where it should not be used or alternatives.

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

Deploy Server