Retrieve a single calendar event's details by providing its calendar ID and event ID. Use this to fetch specific event information from Google Calendar.
Get a single calendar event by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| eventId | Yes | Event ID | |
| calendarId | Yes | Calendar ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and openWorldHint annotations already establish that this is a safe read operation with open-world semantics. The description adds only the 'single event' scoping but does not disclose return shape, error behavior, or external-change caveats beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler. It front-loads the action, resource, and identifying constraint, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only fetch with two fully documented required parameters, the description is nearly sufficient. It lacks explicit guidance about using list instead of get and does not describe the response, but those are minor gaps given the tool's simplicity and the annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with 'Event ID' and 'Calendar ID' already documented. The description does not add deeper meaning about ID formats, where to find the IDs, or relationships between the parameters, so it stays at the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), resource ('calendar event'), and scope ('single ... by ID'), which clearly distinguishes it from sibling tools like calendar_events_list, insert, update, and delete. An agent can immediately understand what this tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by ID' implies this tool should be used when the agent already has an eventId and calendarId, but it does not explicitly mention when to prefer alternatives such as calendar_events_list. Usage context is only implied, not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.