Skip to main content
Glama

calendar list calendars

calendar_list_calendars
Read-onlyIdempotent

List calendars visible to the connected Google account, including each calendar's access role, so you can identify available calendars before reading or scheduling events.

Instructions

List calendars visible to the connected account with access roles.

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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds one useful behavioral fact beyond that: results include access roles. It says nothing about pagination, ordering, or whether hidden/secondary calendars are included, which keeps it at a baseline 3.

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?

One sentence, front-loaded with the verb and resource, with the scoping qualifier and the returned attribute attached. There is no boilerplate, no repetition of the title, and nothing that could be trimmed without losing meaning.

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?

For a zero-parameter read-only list tool with rich annotations and an output schema, the description covers what the tool returns at a high level, so an agent can call it correctly. The only gap is discovery context (whether primary/hidden calendars appear, ordering), which is minor given the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the schema imposes no semantic burden, and the description correctly avoids restating an empty schema. The single clarifying detail ("with access roles") is the only thing an agent could not get from the schema, and it is present.

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 calendars") plus the scope ("visible to the connected account") and the payload detail ("with access roles"), so an agent can tell it apart from calendar_list_events or calendar_check_availability by resource. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 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 description never says when to reach for this tool versus alternatives such as calendar_list_events or calendar_check_availability, nor does it note any preconditions. Usage is only inferable from the tool name and the word "List"; no explicit guidance or exclusions are given.

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