Skip to main content
Glama

graph_get_event

Retrieve full details for a specific Microsoft Graph calendar event by ID, choosing HTML or text body format and optionally targeting a shared or delegated user calendar.

Instructions

Get full details of a specific calendar event.

Args: event_id: The event ID. body_type: Body format to request: "html" or "text" (default "html"). Use "text" to avoid pulling large HTML bodies into context. user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

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

Input Schema

NameRequiredDescriptionDefault
userNo
event_idYes
body_typeNohtml

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does well on two fronts: it discloses the delegated/shared permission requirement (Calendars.Read.Shared or Calendars.ReadWrite.Shared) and warns that HTML bodies can bloat context. It never states explicitly that the call is read-only or what happens when the event ID is invalid or inaccessible, leaving part of the safety profile to inference.

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?

The summary sentence is front-loaded and the per-argument notes are grouped cleanly underneath. There is no filler, though the line-wrapped arg block is slightly verbose compared with a single tight paragraph. Nothing written fails to earn its place.

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?

There is no output schema and no annotations, so the description is the only source of information about the response, yet "full details" is never unpacked into what fields come back (attendees, recurrence, times, body). Given three parameters and a getter's dependence on returned shape, the definition is adequate but leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must supply all parameter meaning and it does: it explains the enum values for body_type with a default and a practical rationale, and explains that an empty user targets the caller's own calendar while a populated value requires shared permissions. This is meaning well beyond the bare schema types and defaults.

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 first line names a specific verb and resource ("Get full details of a specific calendar event"), which clearly separates it from list-style siblings such as graph_list_event_instances. It stops short of naming an alternative tool or stating how it differs from graph_get_online_meeting or similar getters, 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?

Usage context is only implied: an agent can infer this is the follow-up call after identifying an event ID. The body_type guidance ("Use 'text' to avoid pulling large HTML bodies into context") is genuinely useful decision guidance, but it is about parameter choice rather than when to choose this tool over a sibling. No exclusions or prerequisites for calling are stated.

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