Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

get_calendar_event

Read-onlyIdempotent

Retrieve complete details for a single Outlook calendar event by event ID to review times, attendees and responses, body, meeting link, and recurrence.

Instructions

Full details of one event: times, attendees and responses, body, meeting link, recurrence.

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_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesevent_id from list_calendar_events or search_calendar
timezoneNoIANA timezone for input and output times (default: this Mac's zone)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description need not restate it. It adds real value by disclosing the returned content, particularly 'attendees and responses' and 'meeting link', which an agent cannot infer from annotations and which matters given there is no output schema.

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

Conciseness5/5

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

A single front-loaded fragment with zero filler; every element in the field list earns its place by telling the agent what it will receive. No restructuring would improve it.

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 two-parameter read tool with rich annotations and no output schema, the description is nearly complete because it enumerates the return payload. Minor gaps remain around recurring-event handling (master vs. instance) and behavior for a missing or unauthorized event_id.

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 both event_id and timezone are fully documented in the schema, including the default zone behavior. The description adds no meaning beyond that, so the 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?

The description names a specific resource and scope ('Full details of one event') and enumerates what is returned (times, attendees and responses, body, meeting link, recurrence), which clearly distinguishes it from a list or search tool. It stops short of naming any sibling explicitly, so it earns a 4 rather than 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?

There is no explicit when-to-use or when-not statement and no named alternative. Usage is only implied: 'one event' signals a single-record fetch that naturally follows a listing or search call, and the required event_id makes the precondition obvious.

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