Skip to main content
Glama

List Planner Tasks

list_planner_tasks
Read-only

Retrieve tasks from a Microsoft Planner plan by plan ID, with optional fetching of all result pages to view the complete task list.

Instructions

List tasks 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": "list_planner_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesPlan ID
fetch_all_pagesNoFetch all pages of results (max 50 pages)

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?

readOnlyHint=true already establishes that this is a safe read, so the description needs to add the operational context instead. It adds none: no mention of pagination behavior or the default page size, no ordering of returned tasks, and no hint that fetch_all_pages can cap out at 50 pages. With annotations covering safety, the description contributes essentially nothing beyond the title.

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 short sentence with no filler, and the resource scope is front-loaded. It is efficient, though the brevity is closer to under-specification than to disciplined concision.

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 two-parameter read-only list tool with full schema coverage and a readOnlyHint, the definition is minimally viable. It is still missing pagination defaults and the prerequisite of having a plan_id, which an agent would need to call this correctly on the first attempt.

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%, so both plan_id and fetch_all_pages are documented in the schema and the baseline of 3 applies. The description does not explain how to obtain a plan_id or what the default behavior is when fetch_all_pages is omitted, so it adds no meaning beyond the schema.

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 states a specific verb and resource: 'List tasks in a Planner plan'. That is enough to distinguish it from create_planner_task, get_planner_task, and list_planner_buckets by name and resource alone. It stops short of any explicit sibling differentiation, but the resource scope 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. Nothing tells the agent how this differs from get_planner_task for a single task, or that list_plans should be called first to obtain a plan_id. The agent must infer the retrieval workflow from sibling names.

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