Skip to main content
Glama

get-calendar-event

Read-only

Retrieve detailed calendar event information from Microsoft 365, including properties, relationships, HTML body content, and custom extensions for specific event IDs.

Instructions

Get the properties and relationships of the specified event object. Currently, this operation returns event bodies in only HTML format. There are two scenarios where an app can get an event in another user's calendar: Since the event resource supports extensions, you can also use the GET operation to get custom properties and extension data in an event instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectNoSelect properties to be returned
expandNoExpand related entities
eventIdYesPath parameter: eventId
fetchAllPagesNoAutomatically fetch all pages of results
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
timezoneNoIANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
expandExtendedPropertiesNoWhen true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.
Behavior4/5

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

Adds valuable behavioral details beyond annotations: specifies HTML-only format for bodies, and explains extension/custom property support (relevant to openWorldHint). Annotations cover safety profile (readOnly).

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?

First two sentences are efficient. Contains a structural defect: incomplete sentence fragment about 'two scenarios' ending with a colon. Final sentence is slightly verbose ('you can also use the GET operation').

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?

Covers output format (HTML) and extensions adequately for a read operation with good annotations and parameter documentation, but the incomplete delegation scenarios leave a gap regarding cross-user permissions.

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 has 100% coverage so baseline is 3. Description provides context for expandExtendedProperties by mentioning custom properties and sync metadata, but does not elaborate on other parameters like timezone or select/expand patterns.

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?

Clear verb (Get) and resource (calendar event properties/relationships), but fails to distinguish from siblings like get-specific-calendar-event or get-calendar-view.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this versus list-calendar-events or get-calendar-view. Begins to mention cross-user calendar access scenarios but leaves the sentence incomplete after the colon.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alfredo-ia/ms-365-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server