Microsoft 365 MCP Server

tentatively-accept-calendar-event

tentatively-accept-calendar-event

Destructive

Respond tentatively to a calendar event to show you may attend. If the scheduled time conflicts, propose an alternative time directly in the response.

Instructions

Tentatively accept the specified event in a user calendar. If the event allows proposals for new times, on responding tentative to the event, an invitee can choose to suggest an alternative time by including the proposedNewTime parameter. For more information on how to propose a time, and how to receive and accept a new time proposal, see Propose new meeting times.

💡 TIP: Tentatively accepts a meeting invitation. Optional body: { sendResponse: true, comment: 'I might be able to attend.' }. Use proposedNewTime to suggest an alternative: { proposedNewTime: { start: { dateTime, timeZone }, end: { dateTime, timeZone } } }.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes
`confirm`	No	For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
`eventId`	Yes	Value 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.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedv0.145.2Aug 22, 2026

removedInput schema / $defs

Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "dateTime": {
-        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-        "type": "string"
-      },
-      "timeZone": {
-        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  }
-}

changedInput schema / properties / body / properties / ProposedNewTime / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "end": {
-        "$ref": "#/$defs/def0"
-      },
-      "start": {
-        "$ref": "#/$defs/def0"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "end": {
+        "additionalProperties": true,
+        "properties": {
+          "dateTime": {
+            "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+            "type": "string"
+          },
+          "timeZone": {
+            "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "start": {
+        "additionalProperties": true,
+        "properties": {
+          "dateTime": {
+            "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+            "type": "string"
+          },
+          "timeZone": {
+            "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]

Changed3 schema fields changedv0.134.4Jul 28, 2026

addedInput schema / $defs

Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "dateTime": {
+        "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
+        "type": "string"
+      },
+      "timeZone": {
+        "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

changedInput schema / properties / body / properties / ProposedNewTime / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "end": {
-        "additionalProperties": true,
-        "properties": {
-          "dateTime": {
-            "description": "A single point of time in a combined date and time representation ({date}T{time}; for example, 2017-08-29T04:00:00.0000000).",
-            "type": "string"
-          },
-          "timeZone": {
-            "description": "Represents a time zone, for example, 'Pacific Standard Time'. See below for more possible values.",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "start": {
-        "$ref": "#/properties/body/properties/ProposedNewTime/anyOf/0/properties/end"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "end": {
+        "$ref": "#/$defs/def0"
+      },
+      "start": {
+        "$ref": "#/$defs/def0"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]

changedInput schema / properties / eventId / description

Previous value: -"Path parameter: eventId"New value: +"Value 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."

Addedv0.131.2Jul 18, 2026
Removedv0.131.2Jul 18, 2026

Changed1 schema field changedv0.131.1Jul 11, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: \"confirmation_required\" } without touching user data.",
+  "type": "boolean"
+}

Addedv0.114.0May 28, 2026
Removedv0.112.2May 22, 2026
Addedv0.110.0May 18, 2026
Removedv0.108.0May 15, 2026
Addedv0.96.0May 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=true, so the description doesn't need to repeat that it mutates state. It adds context about the proposedNewTime mechanism and the sendResponse/comment fields, which is useful. However, it does not disclose side effects like sending a response or that the event is modified in the calendar. Given the annotations already cover safety, this is acceptable but could be richer.

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 core action is front-loaded in the first sentence. The tip paragraph is an efficient addition with a concrete example. No fluff, but the description is not overly brief; it earns each sentence. Slightly verbose with the second paragraph, but it adds practical value.

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?

The tool has multiple nested parameters and no output schema. The description does not explain return values or error behavior, which agents might need. However, given the similarity to other calendar event tools, the response format may be assumed. The confirm gate and headers/flags are described in the schema, so the description doesn't need to repeat them. Still, a brief note on what to expect in response would improve completeness.

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 80%, so the schema already documents most parameters. The description adds a concrete example for the body object in the tip, but this largely duplicates schema content. It does not clarify the 'confirm' parameter beyond what the schema states (which already explains when it is required). Baseline 3 is appropriate.

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?

States a clear action ('Tentatively accept') on a specific resource ('the specified event in a user calendar'). The name itself differentiates from siblings like accept-calendar-event and decline-calendar-event, and the description reinforces this by focusing on tentative acceptance and optional proposal.

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

Usage Guidelines4/5

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

Provides clear context for using the tool (tentatively accepting an event) and mentions the optional proposal flow. Does not explicitly contrast with alternatives (e.g., 'use accept-calendar-event for final acceptance'), but the action is self-evident from the name and description. The tip gives concrete examples of body parameters, enhancing usability.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/Softeria/ms-365-mcp-server'

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