Skip to main content
Glama

Read Calendar Event

get_event
Read-only

Retrieve detailed calendar event information, including plain-text body and Teams invite join links with meeting IDs and passcodes.

Instructions

Get detailed information about a calendar event. The body comes back as plain text by default; a Teams invite's text still includes its join link and any meeting ID and passcode.

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_idYesThe event ID
time_zoneNoShow times in this zone: an IANA name (America/New_York) or a Windows one (Eastern Standard Time). Default: UTC. Pass the user's own zone to read times as they would.
body_formatNoBody format: 'text' (default) has Graph strip the HTML server-side; 'html' returns the raw markup
calendar_idNoID of the calendar the event is in, from list_calendars. Needed for a calendar shared with you by someone else; may be omitted for your own calendars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description adds genuine value by disclosing return-content behavior — body as plain text by default and that Teams invites retain join link, meeting ID and passcode — but says nothing about the rest of the payload (times, attendees, recurrence) or about failure when an event is missing.

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?

Two tight sentences, with the core purpose front-loaded and the output caveat second. Every clause carries information; only minor redundancy with the body_format schema note.

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?

With no output schema, the description must carry the return-value burden and only covers body formatting. For a four-parameter read tool, an agent still lacks a picture of what 'detailed information' includes, so it is adequate but incomplete.

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 event_id, time_zone, body_format and calendar_id are all documented in-schema, including the UTC default and the IANA/Windows zone formats. The description adds no parameter meaning beyond restating the default body-as-text behavior, 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?

States a specific verb and resource: 'Get detailed information about a calendar event.' An agent can tell this is a single-event read, distinct from list-oriented siblings like list_calendar_view, though the description never names that distinction explicitly.

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: the singular 'a calendar event' plus the required event_id suggests one-item retrieval, but there is no explicit when-to-use vs list_calendar_view or get_meeting_transcript, and no stated prerequisite such as needing an ID from a prior listing call.

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