Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-my-calendar-permission

create-my-calendar-permission
Destructive

Share or delegate your Microsoft 365 calendar to another user by specifying their email and access role. Creates the calendar permission and returns its ID for later updates or removal.

Instructions

Create a calendarPermission resource to specify the identity and role of the user with whom the specified calendar is being shared or delegated.

šŸ’” TIP: Shares the user's primary calendar with another user (or sets up a delegate). Body: { emailAddress: { name: 'Adele Vance', address: 'adele@contoso.com' }, role: 'read' | 'write' | 'delegateWithoutPrivateEventAccess' | 'delegateWithPrivateEventAccess', isInsideOrganization: true, isRemovable: true }. Use list-users to resolve the recipient SMTP. Returns the created calendarPermission with its id (used by update-my-calendar-permission and delete-my-calendar-permission).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
confirmNoFor 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.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude 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.

  1. Changed5 schema fields changedv0.145.2
    • removedInput schema / $defs
      Removed value: -{
-  "def0": {
-    "enum": [
-      "none",
-      "freeBusyRead",
-      "limitedRead",
-      "read",
-      "write",
-      "delegateWithoutPrivateEventAccess",
-      "delegateWithPrivateEventAccess",
-      "custom"
-    ],
-    "type": "string"
-  }
-}
    • changedInput schema / properties / body / properties / allowedRoles / items / anyOf
      Previous value: -[
-  {
-    "$ref": "#/$defs/def0"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "enum": [
+      "none",
+      "freeBusyRead",
+      "limitedRead",
+      "read",
+      "write",
+      "delegateWithoutPrivateEventAccess",
+      "delegateWithPrivateEventAccess",
+      "custom"
+    ],
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {},
+    "type": "object"
+  }
+]
    • removedInput schema / properties / body / properties / role / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / role / enum
      Added value: +[
+  "none",
+  "freeBusyRead",
+  "limitedRead",
+  "read",
+  "write",
+  "delegateWithoutPrivateEventAccess",
+  "delegateWithPrivateEventAccess",
+  "custom"
+]
    • addedInput schema / properties / body / properties / role / type
      Added value: +"string"
  2. Addedv0.134.4
  3. Removedv0.131.2
  4. Changed1 schema field changedv0.131.1
    • 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"
+}
  5. Addedv0.114.0
  6. Removedv0.112.2
  7. Addedv0.110.0
  8. Removedv0.108.0
  9. Addedv0.105.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint: false) and destructiveHint: true, so the bar is lower. The description adds the effect (shares primary calendar or delegates) and provides an example body, plus the return value includes an id for later modifications. It does not contradict annotations.

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 concise sentences plus a tip. The purpose is front-loaded, and the tip provides a concrete example and return information without unnecessary verbosity. Every word earns its place.

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?

Covers purpose, example body, return value, and relationship to update/delete siblings. It doesn't explicitly state that the tool targets the user's primary calendar only, but that is implied by the naming convention (create-my-calendar-permission) and sibling tools. No output schema, but the return is described adequately.

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 coverage is 75%, so the description doesn't need to carry the full burden. The tip provides an example body with typical role values, but the enumerated roles listed are an incomplete subset of the schema's full enum (missing 'none', 'freeBusyRead', etc.), which could slightly mislead. However, the schema itself has the full list, so this is not a major issue.

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 a specific verb and resource: 'Create a calendarPermission resource to specify the identity and role of the user with whom the specified calendar is being shared or delegated.' It distinguishes itself from update/delete siblings by mentioning the returned id is used for those operations. The tip clarifies it shares the user's primary calendar or sets up a delegate.

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?

The tip explains when to use the tool (sharing primary calendar, delegating) and directs the agent to use list-users to resolve email addresses. It also notes the return id is used by update and delete tools, providing chaining context. It doesn't explicitly state when not to use, but the intent is clear.

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

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