Skip to main content
Glama

Create Planner Task

create_planner_task
Destructive

Create a new Microsoft Planner task with a title and plan ID, plus optional due date, bucket, and assignees, to organize work and track assignments.

Instructions

Create a new 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>",
      "title": "<title>"
    },
    "name": "create_planner_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTask title
plan_idYesPlan ID
due_dateNoDue date (ISO format)
bucket_idNoBucket ID
assignmentsNoComma-separated user IDs to assign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write semantics are covered structurally. The description adds nothing beyond that: it does not state permission requirements, whether a bucket or plan must pre-exist, or what the caller receives back (the new task id), which matters for a create operation whose result is typically needed for follow-up calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but its brevity comes from omission rather than efficiency. There is no wasted wording, yet nothing of substance is delivered either.

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?

For a five-parameter create tool marked destructive with no output schema, the description should at minimum state prerequisites and the returned identifier. It supplies neither, leaving the agent to infer everything from the input schema.

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%, with all five parameters documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema — notably it does not clarify the comma-separated string encoding for assignments or ISO formatting expectations, both of which are only visible in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a verbatim restatement of the tool name and title: 'Create a new Planner task'. It names the resource but provides no scope, no distinguishing detail versus siblings such as create_todo_task or create_planner_bucket, and no hint of what a 'Planner task' creation entails.

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, no preconditions (e.g. that the plan must exist), and no mention of alternatives. An agent has no basis in the description for choosing this over create_todo_task when asked to 'add a 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