Skip to main content
Glama

Read Planner Task

get_planner_task
Read-only

Retrieve detailed Microsoft Planner task information by task ID to inspect status, assignments, and due dates before updating or reporting on work.

Instructions

Get detailed Planner task information

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": {
      "task_id": "<task_id>"
    },
    "name": "get_planner_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask 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?

The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description is not required to carry the safety profile. Beyond that, it adds nothing: no statement of what "detailed" includes (checklists, assignments, assignments, attachments), no permission or error behavior, and no indication of whether missing tasks error or return empty.

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 or repetition. It is efficient, though the terseness borders on under-specification rather than tight scoping.

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?

There is no output schema, so the description should explain what is returned, and "detailed" does not do that. For a simple read-by-ID tool this is a modest but real gap, since the agent cannot tell which fields or expansions to expect.

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?

With one parameter at 100% schema description coverage, the schema already documents task_id and the baseline is 3. The description adds no format, sourcing, or ID-context (e.g., where a task ID comes from), so it neither helps nor hurts.

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 names a specific verb ("Get") and resource ("Planner task") and adds "detailed," which signals single-task retrieval of full detail as opposed to the sibling list_planner_tasks. It is clear, but it never explicitly contrasts itself with that sibling, so sibling differentiation is left to inference.

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 and no named alternative. At most, the phrase "detailed ... task information" implies fetching one task by ID, but the agent is given no condition for choosing this over list_planner_tasks or update_planner_task.

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