Skip to main content
Glama
mpalermiti

outlook-mcp

by mpalermiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

outlook_update_event

Update an existing Outlook calendar event by changing its subject, start/end times, location, body, or attendees. Manage recurring event settings or remove recurrence as needed.

Instructions

Update fields on an existing event (partial patch — only provided fields change).

recurrence takes the same shapes as outlook_create_event and converts a single event into a series, or replaces an existing series' pattern. Omit it to leave any recurrence alone; pass remove_recurrence=True to turn a series back into a single event, keeping the first occurrence's time (the two are mutually exclusive). attendees REPLACES the whole guest list (Graph has no add-one operation) and sends invitations to everyone on it plus cancellations to anyone dropped — pass the full intended list; [] removes everyone. is_all_day REQUIRES start and end in the same call, both on midnight boundaries. Omitting an argument leaves it unchanged, so False and [] are instructions, not absences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
bodyNo
startNo
subjectNo
event_idYes
locationNo
attendeesNo
is_all_dayNo
recurrenceNo
remove_recurrenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.19.0
    • addedInput schema / properties / attendees
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Attendees"
+}
    • addedInput schema / properties / is_all_day
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Is All Day"
+}
    • addedInput schema / properties / recurrence
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Recurrence"
+}
    • addedInput schema / properties / remove_recurrence
      Added value: +{
+  "default": false,
+  "title": "Remove Recurrence",
+  "type": "boolean"
+}
  2. First observedv1.11.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing side effects: it sends invitations and cancellations, replaces the entire attendee list, converts events to series, and requires special handling for all-day events. It also clarifies that False and [] are instructions, not omissions, which is crucial behavioral context.

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?

The description is a well-organized paragraph that front-loads the core behavior, then systematically covers each special case without redundancy. Every sentence adds value, and the length is appropriate for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters, no output schema, and no schema-level descriptions, the description covers all critical edge cases: partial updates, recurrence transformation, attendee replacement side effects, all-day constraints, and the distinction between omission and explicit false/empty. It leaves no ambiguous gaps for an agent to misinterpret.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well for the tricky parameters: recurrence, attendees, is_all_day, remove_recurrence, and the mutual exclusion. It explains the semantics of these non-obvious parameters. However, it does not elaborate on the simpler ones like subject, body, start, end, or location, though their meanings are self-evident from names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Update' and resource 'event', and specifies 'partial patch — only provided fields change', which distinguishes it from full-replace operations. It also highlights key capabilities like recurrence handling, making the tool's purpose unambiguous.

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 description explains how parameters behave (e.g., omission leaves unchanged, attendees replace the list) but does not explicitly contrast with sibling tools like outlook_create_event or outlook_delete_event. It implies usage on existing events but never states when to prefer this over alternatives, leaving that inference to the agent.

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