Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get-specific-calendar-event

get-specific-calendar-event
Read-only

Retrieve a single calendar event from a signed-in user's Microsoft 365 calendar using the calendar ID and event ID.

Instructions

Get a single event from one of the signed-in user's calendars, addressed by calendar ID and event ID. Any calendar can be addressed this way, including the default one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoNavigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as a message body fails with "Parsing OData Select and Expand failed", and an unsupported value may be ignored rather than reported. Request ordinary fields with $select instead.
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
eventIdYesValue for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph.
timezoneNoIANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
calendarIdYesValue for the 'calendarId' path segment. Pass it under the name 'calendarId', not as 'id'. Use the 'id' field of the calendar object as returned by Microsoft Graph.
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
expandExtendedPropertiesNoWhen true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.154.2
    • addedInput schema / properties / expand / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / expand / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / expand / type
      Removed value: -"array"
    • addedInput schema / properties / select / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / select / type
      Removed value: -"string"
  2. Addedv0.134.4
  3. Removedv0.131.2
  4. Addedv0.114.0
  5. Removedv0.112.2
  6. Addedv0.110.0
  7. Removedv0.108.0
  8. Changed5 schema fields changedv0.96.0
    • addedInput schema / properties / expandExtendedProperties
      Added value: +{
+  "description": "When true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.",
+  "type": "boolean"
+}
    • changedInput schema / properties / fetchAllPages / description
      Previous value: -"Automatically fetch all pages of results"New value: +"Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search."
    • changedInput schema / properties / select / description
      Previous value: -"Select properties to be returned"New value: +"Comma-separated fields to return, e.g. id,subject,from,receivedDateTime"
    • removedInput schema / properties / select / items
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / properties / select / type
      Previous value: -"array"New value: +"string"
  9. First observedv0.31.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive behavior, so the description does not need to restate that. It adds the useful scoping fact that the default calendar is also addressable, but it does not disclose error behavior or return shape. With annotations covering the safety profile, this is adequate but not rich.

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?

Two sentences, front-loaded with verb and resource, with no filler. The second sentence earns its place by scoping the tool to any calendar, including the default one.

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 read operation with fully documented parameters and read-only annotations, the description plus schema is largely complete. The main gap is the absence of explicit guidance for choosing this over get-calendar-event or list-specific-calendar-events, and there is no output-shape note since no output schema exists.

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% and each parameter already has detailed documentation, so the baseline is 3. The tool description only repeats calendarId and eventId in prose and adds no new meaning beyond what the schema provides.

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 clearly names the operation ('Get a single event') and the resource scope ('one of the signed-in user's calendars'), and the addressing mechanism by calendar ID and event ID separates it from event-list tools. It does not explicitly contrast with the sibling tool get-calendar-event, so it stops short of full sibling differentiation.

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?

The prose implies the right context: use this when you have both calendarId and eventId and need a single event. The second sentence clarifies that any calendar is addressable, including the default one, but no alternative tool is named and no when-not-to-use guidance is given.

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