Skip to main content
Glama

Calendar: Get event

calendar_get_event
Read-onlyIdempotent

Get one event using both its exact parent calendar_id and event_id. Never identify an event only by title or date. Google may read an accessible public calendar by ID even outside the private calendar list; Outlook stays account-bound.

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>",
      "event_id": "<event_id>"
    },
    "name": "calendar_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesExact event ID returned by calendar_list_events or calendar_create_event, paired with its parent calendar_id. Calendar event ID: Exact event id in the selected calendar/account. Obtain with: calendar_list_events -> event.id; calendar_create_event -> created event.id Never pass: event title, date.
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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful provider nuance — Google can read a public calendar by ID outside the private calendar list while Outlook is account-bound — but says nothing about behavior on a missing/unauthorized event or cross-account access failures.

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 plus one short provider clause; the lookup requirement is front-loaded and the anti-pattern warning follows immediately. No filler or restatement of the tool name.

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 read-only single-resource get with full schema coverage and no output schema, the definition covers what is needed to invoke correctly, including ID sourcing rules and cross-provider access nuance. It omits what the returned event object looks like and error semantics, which is a minor gap for a get 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 coverage is 100%, so the baseline is 3 and the schema already carries the 'never pass title or date' guidance. The description does add the relational constraint that event_id must be paired with its exact parent calendar_id, which explains scoping/namespacing, but the rest largely echoes structured fields.

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?

The description gives a specific verb and resource ('Get one event') plus the scoping requirement that both parent calendar_id and event_id are needed, which distinguishes it from the listing siblings by implication. It stops short of explicitly naming calendar_list_events as the alternative path, so differentiation is inferred rather than stated.

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 supplies a clear negative rule: never identify an event by title or date, only by exact IDs. It gives the required context for invocation but does not spell out the proactive workflow (list first, then get) or when a caller should prefer a search/list tool instead.

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.