Skip to main content
Glama

Create Planner Bucket

create_planner_bucket
Destructive

Creates a new bucket (column) in a Microsoft Planner plan, letting you organize tasks into custom stages or categories. Provide the plan ID and bucket name.

Instructions

Create a new bucket (column) in a Planner plan

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>",
      "name": "<name>"
    },
    "name": "create_planner_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBucket name
plan_idYesPlan ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description only needs to add context such as permission requirements or where the new column lands relative to existing ones — it adds none. The word 'create' does not conflict with the annotations, but the surprising destructiveHint=true on a pure-create tool is never explained or reconciled, leaving a behavioral question the agent must guess at.

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?

A single front-loaded sentence with no filler and no repetition of the title. It is efficient, though the brevity is bought by leaving behavioral and prerequisite context out entirely.

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?

For a simple two-parameter create tool with full schema coverage, annotations, and no output schema, the description is minimally sufficient to identify the action. It falls short of complete because it omits preconditions (target plan must exist, required write scope) and any hint about the result of 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?

Schema coverage is 100%, with both plan_id and name already documented in the schema, so the schema carries the parameter burden. The description adds only the parenthetical that a bucket is a column; it says nothing about the format of plan_id (e.g., that it must be an existing plan's identifier) or any name uniqueness or length constraints.

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 uses a specific verb and resource ('Create a new bucket') and adds a useful gloss ('column') that tells an agent what a Planner bucket actually is. The resource is distinct enough from siblings like create_planner_task or list_planner_buckets, though no sibling is named or excluded explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as the plan needing to exist or the caller needing Planner/group write permissions, and no pointer to list_planner_buckets to check for an existing bucket first. Usage is only inferable from the tool name.

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