Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__calendar_list_calendars

Read-only

Lists the calendars on the connected account's calendar list: its own, shared ones it has added, and subscribed ones such as holidays. Returns one compact entry per calendar: its ID, title, whether it is the primary calendar, the account's access role (owner, writer, reader or freeBusyReader) and its time zone, plus a page token when more remain. The ID is what calendar_list_events and the other calendar tools take as calendar_id.

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": "gws-mcp__calendar_list_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_tokenNoThe nextPageToken from an earlier call, to read the page after it.
max_resultsNoThe most calendars to return in one page (default: 50, at most 250).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely new behavior: it discloses the return shape (one compact entry per calendar), the fields returned (ID, title, primary flag, access role, time zone), and that a page token appears when more results remain — none of which is in the annotations or schema.

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?

Two sentences, both front-loaded with the most useful information: what is listed first, then what comes back and how to use the ID. No filler and no repetition of schema fields.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing returns, and it does so adequately by naming every returned field and the pagination token. Combined with a fully documented schema and a readOnly annotation, an agent has everything needed to call this correctly.

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 account, page_token and max_results are already fully documented in the schema, including the default of 50 and the 250 cap. The description adds no parameter-level detail beyond mentioning that a page token is returned when more remain, so the baseline 3 applies.

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?

States a specific verb and resource ("Lists the calendars on the connected account's calendar list") and enumerates the three scopes it covers: own, shared, subscribed. It also distinguishes itself from calendar_list_events by explaining that this tool supplies the calendar_id that tool consumes.

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 final sentence gives clear operational context: the returned ID is the calendar_id input for calendar_list_events and the other calendar tools, which implies this is the discovery step before any per-calendar call. It stops short of an explicit exclusion (e.g. "do not use to find events"), so a 4 rather than 5.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources