Skip to main content
Glama

gcal_list_calendars

Lists calendars in a connected Google account, returning each calendar's ID, name, and primary status so you can pick the right one for scheduling or event tasks.

Instructions

(Beta) List the calendars of a connected Google account (Google Calendar): id, name, whether it is the prim...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.4/5.0
Behavior3/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. 'List' plus the field enumeration signals a read-only, non-destructive call and hints at the return shape, but there is no statement about pagination, account scoping, or whether disconnected accounts error — and the '(Beta)' marker is never explained.

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 content is front-loaded and dense with no wasted clauses, but the text terminates mid-sentence at 'whether it is the prim…', leaving the field enumeration and likely any trailing caveats unresolved. That truncation is a real structural defect an agent must work around.

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?

For a zero-parameter discovery tool with no output schema, the description should fully describe the returned record, and it starts to (id, name, primary) but is cut off before completing the list. The beta qualification is also left unexplained, so an agent cannot tell what about the behavior is unstable.

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?

The schema is an empty object with zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not add a hidden scoping parameter or filter concept, which is consistent with the schema.

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 the calendars of a connected Google account' — and enumerates the returned fields (id, name, primary flag), so the agent knows exactly what this returns. It does not distinguish itself from nearby siblings such as list_calendar_names or the other gcal_* tools, and the trailing truncation cuts the enumeration short.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool clearly serves 'which calendars exist for this connected account' discovery, which is a prerequisite for the calendar-id-taking siblings. There is no explicit when-to-use, no exclusion, and no pointer to the alternative list_calendar_names tool that appears to overlap.

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