Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

calendar_events_get

Read-only

Retrieve a single Google Calendar event using its calendar ID and event ID to view event details for scheduling, auditing, or integration needs.

Instructions

Get 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": {
      "calendarId": "<calendarId>",
      "eventId": "<eventId>"
    },
    "name": "calendar_events_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent ID
calendarIdYesCalendar ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description contributes nothing further. It does not mention behavior on an unknown or deleted event ID, permission/scope requirements, or whether recurring-event instances are supported.

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 no filler, and the identifying scope ('single', 'by ID') comes before any caveats. It is lean to the point of leaving gaps, but nothing is wasted.

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?

For a two-parameter read tool with complete schema coverage and annotations covering safety, minimal prose is defensible. However, with no output schema the description could still say what a returned event contains or that it fails for missing/inaccessible events.

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 both calendarId and eventId are documented in the schema, and the description only echoes that the lookup is by ID. It adds no meaning such as whether calendarId can be 'primary' or what format the event ID takes; baseline 3 applies.

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 states a specific verb (Get) and resource (a single calendar event) with the lookup key (by ID), which cleanly separates it from calendar_events_list and the mutation siblings. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"By ID" implies the tool is for fetching one already-known event rather than searching or enumerating, which is useful implied guidance. There is no explicit when-to-use/when-not statement and no pointer to calendar_events_list for discovery.

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