Skip to main content
Glama

Read an event

events_get
Read-only

Read one event whole, by the account, calendarId and id events_list names: its whole description as text, every Teams, Zoom or Meet join link found in the event, its place or its words, the organizer and each guest with their role - required, optional or resource - and answer, its kind and privacy as events_list names them, how it shows, the account's own answer, its reminders - the minutes before its start each sounds, or none, which events_edit writes as an empty list, and unsaid where a Google event keeps its calendar's own - and its web link. Times are given as events_list gives them, in the zone named under timeZone, and an occurrence of a recurring series its seriesId and originalStart as events_list names them. An event whose words screen as a prompt attack is withheld. One of Lumman's own busy copies is answered under busyCopy as events_list answers one, saying under about what it is and where it is switched off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesThe connected account, by the address calendars_list names.
eventIdYesThe event's id, as events_list names it.
providerNoThe account's provider, as calendars_list names it; needed only where two connected accounts share an address.
timeZoneNoAn IANA zone such as Europe/London to answer in; the person's stored one where omitted.
calendarIdNoThe calendar holding the event, by the calendarId events_list names; an event outside the account's default calendar needs it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/destructive/openWorld, and the description adds substantial behavior beyond them: events whose text screens as a prompt attack are withheld, Lumman's own busy copies are answered under busyCopy with about/switched-off fields, and reminders are reported as minutes or an empty list. These are real edge-case behaviors an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, and given the absence of an output schema, the enumeration of returned fields earns its place. However, it is delivered as one extremely dense run-on sentence with heavy nesting, which hurts parseability rather than being genuinely concise.

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

Completeness5/5

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

With no output schema, the description carries the full return-value burden and does so thoroughly: join links, organizer/guest roles and answers, kind, privacy, visibility, reminders, web link, timeZone handling, recurrence fields (seriesId, originalStart), the prompt-attack withholding rule, and the busyCopy variant. Nothing material for a correct call is missing.

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 schema already documents account, eventId, provider, timeZone and calendarId, including when provider and calendarId are needed. The description reinforces that output times follow the timeZone parameter, but adds little new meaning about the parameters themselves; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening establishes a specific verb and resource ('Read one event whole') and immediately scopes it as 'by the account, calendarId and id events_list names,' which cleanly separates it from the list-oriented sibling events_list. An agent can distinguish it from events_edit and events_list without opening any schema.

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?

Usage is implied through repeated references to sibling conventions ('as events_list names them', 'which events_edit writes as an empty list'), but there is no explicit when-to-use statement or exclusion such as 'use events_list to discover ids first' or 'use busyCopy for a busy view only.' The agent must infer the call context.

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.

Resources