Skip to main content
Glama

List Planner Buckets

list_planner_buckets
Read-only

Lists the buckets (columns) in a Microsoft Planner plan and returns their IDs. Use a bucket ID with create_planner_task to place new tasks in the correct column.

Instructions

List the buckets (columns) in a Planner plan. Use a bucket ID with create_planner_task.

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": "list_planner_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesPlan ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and 'List' is consistent with that. The description adds the useful framing that results are bucket columns scoped to a plan, but says nothing about ordering, empty results, pagination, or permissions, so it adds only modest value beyond the 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 short sentences with zero filler; the core operation is front-loaded and the follow-up usage note is secondary. Every sentence 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?

For a one-parameter read-only list tool with full schema coverage and a readOnlyHint, this is nearly complete: it names the resource, the scope, and the downstream consumer. The only omission is any hint about result shape or ordering, which is minor here.

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 100% for the single plan_id parameter, so the schema already carries the parameter documentation. The description's phrase 'in a Planner plan' reinforces the scoping but adds no format or constraint detail beyond what is structured.

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 and resource: 'List the buckets (columns) in a Planner plan', and even clarifies that buckets are columns, which disambiguates the domain term. It stops short of distinguishing itself from siblings like list_plans, but the operation itself is 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 second sentence ('Use a bucket ID with create_planner_task') gives a downstream usage hint that implies why an agent would call this tool. However, there is no explicit when-to-use/when-not guidance and no comparison to list_plans or create_planner_bucket, so the agent must infer the selection criteria.

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