Skip to main content
Glama

calendar get event

calendar_get_event
Read-onlyIdempotent

Retrieve details of a single Google Calendar event by its ID, optionally specifying a calendar ID (defaults to primary), to inspect event data.

Instructions

Fetch a single calendar event by ID.

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

Input Schema

NameRequiredDescriptionDefault
event_idYes
calendar_idNoprimary

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld behavior, so the description's burden is light, but it adds nothing on top: no error/not-found behavior, no note that calendar_id defaults to the primary calendar, and no hint about expansion of recurring events or attendee/timezone handling.

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?

A single front-loaded sentence with zero filler; nothing is redundant. It is arguably too terse for a 2-parameter tool, but that is a completeness issue rather than a conciseness one.

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?

The tool is simple and an output schema exists, so return values need no explanation. Still, the definition leaves the calendar_id default, not-found behavior, and cross-calendar lookup semantics unaddressed, which an agent would need before calling reliably.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that the lookup is by ID, but says nothing about the optional calendar_id parameter or its 'primary' default, leaving half the parameters undocumented in both the schema and the prose.

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 (fetch) and resource (a single calendar event) restricted to ID lookup, which implicitly separates it from calendar_list_events and calendar_check_availability. It does not name any sibling explicitly, so sibling 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 Guidelines2/5

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

There is no guidance on when to use this versus calendar_list_events, calendar_check_availability, or the create/update/delete siblings. The description gives no preconditions, no mention of what happens when the ID is unknown, and no note about which calendar scope applies.

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