Skip to main content
Glama

Calendar: Get calendar

calendar_get_calendar
Read-onlyIdempotent

Read one calendar by exact provider ID, normally resolved with calendar_list_calendars. Google can also read accessible public calendars by ID; this lookup is not restricted to the private calendar list. Outlook stays account-bound. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendar_id": "<calendar_id>"
    },
    "name": "calendar_get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
calendar_idYesExact calendar ID returned by calendar_list_calendars; never pass a calendar name. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context the annotations cannot convey: Google lookups are not restricted to the private calendar list and can reach accessible public calendars, while Outlook lookups stay account-bound. It says nothing about failure behavior for an unknown ID, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operative guidance is front-loaded and the whole thing is a few lines. The trailing 'Calendar ID: ... Obtain with: calendar_list -> calendar.id Never pass: ...' fragment duplicates the schema description almost word for word, and it abbreviates the sibling as calendar_list rather than calendar_list_calendars.

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 single-resource read with full annotation coverage and complete parameter documentation, the description says enough to invoke it correctly, including provider caveats. With no output schema, a brief note on what a calendar record contains would have made it fully self-sufficient.

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 coverage is 100% and the schema already documents both calendar_id and account_id in detail, including the 'never pass a name' rule. The description largely restates the calendar_id text verbatim, adding only the marginal note that public Google calendars qualify; that is baseline-3 territory where the schema does the heavy lifting.

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 ('Read one calendar') plus the exact-key constraint ('by exact provider ID'), which is enough to separate it from calendar_list_calendars. The provider-specific clauses (Google public calendars readable by ID, Outlook account-bound) further pin down what 'one calendar' means.

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?

It routes the agent through calendar_list_calendars to obtain the ID and warns never to pass a display name, which is genuine when-to-use and how-to-obtain guidance. It does not explicitly contrast with listing multiple calendars or say what to do when the ID lookup fails, so it stops short of full coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.