Skip to main content
Glama

Get event

get_event
Read-only

Retrieve full calendar event details including description, attendees and responses, organizer, online meeting link, and recurrence master by event ID, with text or HTML body and optional truncation.

Instructions

Get full event details: description, attendees with their responses, organizer, online meeting link, recurrence master.

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": {
      "id": "<id>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent ID
formatNoBody format: "text" (default) or "html"
maxBodyCharsNoTruncate the body after this many characters (default 20000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already supply readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by enumerating what detail is returned, but it does not mention that the body can be truncated via maxBodyChars or discuss errors/permissions, leaving behavioral gaps.

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 a compact field list; no filler. Slightly list-like but efficient and scannable.

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

Completeness4/5

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

For a simple three-parameter read tool with full schema coverage and annotations, the description is largely sufficient, and because there is no output schema, its field enumeration usefully covers the return shape. Only truncation/error behavior is left unaddressed.

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%, so id, format, and maxBodyChars are fully documented in the schema itself. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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 and resource ("Get full event details") and enumerates the returned fields (description, attendees, organizer, meeting link, recurrence master), which clearly separates it from list_events. It does not explicitly name a sibling alternative, keeping it just short of a 5.

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 only implied: fetch a single event by ID for full detail. There is no explicit statement about when to prefer this over list_events or when an event ID is unavailable, so guidance is adequate but thin.

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