Skip to main content
Glama

List Planner Plans

list_plans
Read-only

List all Microsoft Planner plans visible to you, aggregated across your group memberships, to quickly find and review plans you can access.

Instructions

List all Planner plans visible to you, aggregated across your group memberships

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's added value is the scope disclosure: results are limited to plans visible to the caller and are aggregated across every group membership rather than scoped to one group. That is a non-trivial behavioral trait that prevents a wrong assumption about needing a group filter. It does not mention pagination, ordering, or result-size behavior, which keeps it short of a 5.

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?

A single sentence with the resource claim first and the scoping constraint second, with no filler or restatement of the title. Nothing could be removed without losing meaning.

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 zero-parameter read-only list tool with annotations carrying the safety profile, the basics are covered. However, there is no output schema, and the description says nothing about what a returned plan contains or how large/complete the aggregated result set may be, leaving the agent to discover the return shape at call time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and the phrase "visible to you" correctly signals that no scoping argument exists or is needed.

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?

"List all Planner plans" names a specific verb and resource, and "Planner plans" separates it from the buckets/tasks list siblings by name. The visibility/aggregation qualifier further sharpens the scope, though it never explicitly contrasts itself with the sibling list tools.

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?

Usage is only implied: an agent can infer this is the entry point for discovering plans before drilling into buckets or tasks, but the description states no when-to-use condition, no prerequisites, and no alternative tool. It is adequate but relies on the caller to derive the workflow.

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