Skip to main content
Glama
Sign In
Google MCP

Google MCP

by shayanhoshyari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_event

Retrieve normalized details for a specific Google Calendar event by event ID, with an optional calendar ID to target non-primary calendars.

Instructions

Get normalized details for one Google Calendar event.

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": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesGoogle Calendar event ID
calendar_idNoCalendar ID; defaults to primary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, yet it only vaguely gestures at behavior via "normalized details" without explaining what normalization means, whether it is read-only (implied only by the name "get"), what happens when the event is missing, or what permissions are required. For a tool with zero annotation coverage this is a significant disclosure gap.

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 or repetition. It is efficient, though its brevity contributes to the tool's under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the definition should describe what "normalized details" actually contains, and with no annotations it should also indicate read-only semantics and failure behavior. Neither is covered, leaving an agent unable to predict the response shape.

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 description coverage is 100%, with both event_id and calendar_id (including the "defaults to primary" behavior) documented in the schema. The description adds no syntax or format detail beyond that, so 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?

"Get normalized details for one Google Calendar event" states a specific verb, resource, and cardinality, which distinguishes it from list_events and the mutation siblings. It stops short of explicitly naming an alternative, but the single-event scope is unambiguous.

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 when-to-use guidance, no mention of when to prefer list_events versus this tool, and no note about preconditions such as access to the calendar. The agent must infer usage purely from the name and schema.

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

Deploy Server

Other Tools