Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

planner

Manage plans, tasks, buckets, and user lookups in Microsoft 365 through entity-and-operation routing to create, update, assign, and delete work items.

Instructions

Unified Microsoft Planner management: plans, tasks, buckets, and user lookups. Use entity + operation routing.

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": {
      "entity": "<entity>",
      "operation": "<operation>"
    },
    "name": "planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBucket name
emailNoSingle user email address (for user lookup)
titleNoPlan/Task title
emailsNoMultiple user email addresses (for user lookup)
entityYesThe entity type to operate on
planIdNoPlan ID
taskIdNoTask ID
userIdNoSingle user ID (for assignment operations)
groupIdNoMicrosoft 365 group ID (for plan create)
taskIdsNoTask IDs (for bulk operations)
updatesNoUpdate data (for bulk_update)
userIdsNoMultiple user IDs (for assignment operations)
bucketIdNoBucket ID
operationYesOperation to perform. Plan: list/get/create/update/delete. Task: list/create/update/delete/get/assign/get_details/update_assignments/get_assignments/bulk_update/bulk_delete. Bucket: list/create/update/delete/get_tasks. User: lookup.
orderHintNoOrder hint for bucket positioning
assignedToNoUser ID(s) to assign
dueDateTimeNoDue date in ISO 8601 format
percentCompleteNoCompletion percentage (0-100)
removeAssignmentsNoUser ID(s) to unassign (for update_assignments)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: delete, bulk_delete, and update_assignments are irreversible mutations that go unmentioned. There is no statement of required permissions, whether deletes are soft or hard, what bulk operations do on partial failure, or any pagination/result behavior for list operations.

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?

Two short sentences, front-loaded with the resource scope and followed by the calling convention, with no filler. The compression is appropriate, though the second sentence is terse enough that its meaning depends on the schema's operation enum.

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 19-parameter multi-entity tool with destructive bulk operations, no annotations, and no output schema, the description is far too thin. An agent gets no map of entity/operation pairs to required parameters, no mutation-safety context, and no hint about what list/get calls return.

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% and each parameter already annotates its own scope (e.g. 'for bulk_update', 'for plan create'), so the schema does the heavy lifting. The description adds only the entity/operation routing concept and does not clarify the cross-product of which parameters are required or ignored for each of the 15+ operations.

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 resource domain (plans, tasks, buckets, user lookups) and the routing model, so an agent knows this is a Planner CRUD surface. It does not distinguish itself from adjacent task-like siblings such as todo or teams tasks, so the agent must infer that Planner-specific plans/buckets mean this tool rather than another.

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?

'Use entity + operation routing' tells the agent how to compose a call, and the operation enum enumerates valid operations per entity. However, there is no guidance on when to choose this tool over todo/teams for task work, no prerequisites (e.g. needing a groupId for plan creation), and no warning about which operations are destructive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.