Skip to main content
Glama

Update Planner Task

update_planner_task
Destructive

Update a Microsoft Planner task's title, due date, priority, or completion percentage; set 100% to close it. Pass an ETag only when optimistic concurrency is needed.

Instructions

Update a Planner task (title, percent_complete — 100 closes it — due date, priority). The ETag is auto-fetched if omitted; pass one only to enforce optimistic concurrency.

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

Input Schema

NameRequiredDescriptionDefault
etagNoTask ETag — omit to auto-fetch; pass to enforce concurrency
titleNoNew title
task_idYesTask ID
due_dateNoNew due date (ISO format)
priorityNoPriority (0-10)
percent_completeNoCompletion percentage (0-100; 100 marks complete)

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?

Beyond the annotations, it discloses two real behavioral traits: setting percent_complete to 100 closes the task (the concrete mechanism behind destructiveHint=true) and the ETag is auto-fetched unless supplied. It still omits whether unspecified fields are left untouched or cleared — a material question for a partial-update call flagged destructive — and says nothing about required permissions.

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 tightly written sentences with the verb and field list front-loaded and the concurrency caveat second. No filler, no restatement of the tool name or title.

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?

Adequate for a six-parameter mutation with one required field, full schema coverage, and no nested objects or output schema. The remaining gap is statement of whether it returns the updated task and whether omitted fields are preserved or nulled, which matters given the destructive annotation.

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 every parameter is already documented in structured form, and the description's parenthetical largely restates it ('100 closes it' mirrors '100 marks complete'; the ETag note mirrors the schema's own wording). Baseline 3 applies since the schema carries the semantic load; the description adds no format or range detail beyond it.

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 (Update) and resource (Planner task) and enumerates the mutable fields (title, percent_complete, due date, priority), so the operation is unmistakable. It does not differentiate itself from the sibling update_planner_task_details, so the agent cannot tell from the text which update path applies to which fields.

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 — the reader infers this is the tool for field-level task edits. The one conditional statement, 'pass one [ETag] only to enforce optimistic concurrency,' is parameter-level guidance rather than when-to-use-this-tool guidance, and no alternative sibling is named or excluded.

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