Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

create-planner-bucket

create-planner-bucket
Destructive

Create a new Microsoft Planner bucket to organize tasks within a plan. Specify a bucket name to group related tasks and streamline project workflow.

Instructions

Create a new plannerBucket object.

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. Changed15 schema fields changedv0.145.2
    • removedInput schema / $defs
      Removed value: -{
-  "def0": {
-    "additionalProperties": true,
-    "properties": {
-      "application": {
-        "$ref": "#/$defs/def1"
-      },
-      "device": {
-        "$ref": "#/$defs/def1"
-      },
-      "user": {
-        "$ref": "#/$defs/def1"
-      }
-    },
-    "type": "object"
-  },
-  "def1": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "def2": {
-    "enum": [
-      "automatic",
-      "noPreview",
-      "checklist",
-      "description",
-      "reference"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / properties
      Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / createdBy / $ref
      Removed value: -"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / additionalProperties
      Added value: +true
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / properties
      Added value: +{
+  "application": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "device": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "user": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / createdBy / type
      Added value: +"object"
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / $ref
      Removed value: -"#/$defs/def2"
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / enum
      Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / type
      Added value: +"string"
    • removedInput schema / properties / body / properties / tasks / items / properties / previewType / $ref
      Removed value: -"#/$defs/def2"
    • addedInput schema / properties / body / properties / tasks / items / properties / previewType / enum
      Added value: +[
+  "automatic",
+  "noPreview",
+  "checklist",
+  "description",
+  "reference"
+]
    • addedInput schema / properties / body / properties / tasks / items / properties / previewType / type
      Added value: +"string"
  2. Changed10 schema fields changedv0.134.4
    • addedInput schema / $defs
      Added value: +{
+  "def0": {
+    "additionalProperties": true,
+    "properties": {
+      "application": {
+        "$ref": "#/$defs/def1"
+      },
+      "device": {
+        "$ref": "#/$defs/def1"
+      },
+      "user": {
+        "$ref": "#/$defs/def1"
+      }
+    },
+    "type": "object"
+  },
+  "def1": {
+    "additionalProperties": true,
+    "properties": {
+      "displayName": {
+        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "def2": {
+    "enum": [
+      "automatic",
+      "noPreview",
+      "checklist",
+      "description",
+      "reference"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / body / properties / tasks / items / properties / completedBy / $ref
      Added value: +"#/$defs/def0"
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / additionalProperties
      Removed value: -true
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / properties
      Removed value: -{
-  "application": {
-    "additionalProperties": true,
-    "properties": {
-      "displayName": {
-        "description": "The display name of the identity.For drive items, the display name might not always be available or up to date. For example, if a user changes their display name the API might show the new value in a future response, but the items associated with the user don't show up as changed when using delta.",
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "description": "Unique identifier for the identity or actor. For example, in the access reviews decisions API, this property might record the id of the principal, that is, the group, user, or application that's subject to review.",
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "device": {
-    "$ref": "#/properties/body/properties/tasks/items/properties/completedBy/properties/application"
-  },
-  "user": {
-    "$ref": "#/properties/body/properties/tasks/items/properties/completedBy/properties/application"
-  }
-}
    • removedInput schema / properties / body / properties / tasks / items / properties / completedBy / type
      Removed value: -"object"
    • changedInput schema / properties / body / properties / tasks / items / properties / createdBy / $ref
      Previous value: -"#/properties/body/properties/tasks/items/properties/completedBy"New value: +"#/$defs/def0"
    • addedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / $ref
      Added value: +"#/$defs/def2"
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / enum
      Removed value: -[
-  "automatic",
-  "noPreview",
-  "checklist",
-  "description",
-  "reference"
-]
    • removedInput schema / properties / body / properties / tasks / items / properties / details / properties / previewType / type
      Removed value: -"string"
    • changedInput schema / properties / body / properties / tasks / items / properties / previewType / $ref
      Previous value: -"#/properties/body/properties/tasks/items/properties/details/properties/previewType"New value: +"#/$defs/def2"
  3. Changed1 schema field changedv0.131.2
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  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.96.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already flag this as a write (readOnlyHint=false) and destructive (destructiveHint=true), and the description adds no behavioral context beyond that — no mention of confirm-gate interaction, idempotency, or side effects. For a create operation that modifies data, the description should at least acknowledge that creating the new object has persistent consequences.

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 single sentence is succinct and front-loaded, with no redundant filler. The brevity is a sign of under-specification, which is penalized in other dimensions, but as a structural matter it is appropriately terse for a single-sentence definition.

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

Completeness2/5

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

For a destructive, open-world tool with a deeply nested body schema and no output schema, one sentence is insufficient context. It doesn't say the bucket must belong to an existing plan, what happens if the client supplies a conflicting id, or what the caller should expect after a successful creation.

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?

The schema covers 75% of parameters with descriptive text, including body, planId, confirm, and the nested task fields, so the schema itself carries most of the semantic weight. The description adds nothing about how the parameters combine (e.g., that the bucket needs a valid planId or that body is required).

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?

States a specific verb (Create) and resource (plannerBucket object) plainly, so an agent can identify what the action is. However, it is essentially a restatement of the tool name and provides no distinguishing detail about what a planner bucket is relative to other Planner tools.

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?

Offers no guidance on when to invoke this tool instead of siblings like create-planner-task, list-plan-buckets, or update-planner-bucket. It also fails to mention the prerequisite context (e.g., an existing plan to attach the bucket to) or when the confirm gate applies.

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