Planning System MCP Server

update_plan

Update plan properties atomically including title, description, status, visibility, and metadata. Archive plans as soft-delete with recovery option.

Instructions

Edit any plan property atomically: title, description, status, visibility, GitHub linkage, metadata. Use status='archived' to soft-delete (recoverable via status='active' + restore=true). Hard delete stays REST-only with admin auth.

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

Input Schema

Name	Required	Description
`plan_id`	Yes
`title`	No
`description`	No
`status`	No
`visibility`	No
`metadata`	No	Shallow-merged into existing metadata.
`restore`	No	Required when un-archiving (status: 'archived' → 'active'). Guards against accidental restoration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.8.1Apr 29, 2026

removedInput schema / properties / description / description
```
Removed value: -"New plan description"
```

addedInput schema / properties / metadata

Added value: +{
+  "description": "Shallow-merged into existing metadata.",
+  "type": "object"
+}

removedInput schema / properties / plan_id / description
```
Removed value: -"Plan ID"
```

addedInput schema / properties / restore

Added value: +{
+  "default": false,
+  "description": "Required when un-archiving (status: 'archived' → 'active'). Guards against accidental restoration.",
+  "type": "boolean"
+}

removedInput schema / properties / status / description
```
Removed value: -"New plan status"
```
removedInput schema / properties / title / description
```
Removed value: -"New plan title"
```

addedInput schema / properties / visibility

Added value: +{
+  "enum": [
+    "private",
+    "unlisted",
+    "public"
+  ],
+  "type": "string"
+}

First observedDec 29, 2025

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses atomic updates, soft-delete behavior, recovery option, and that hard delete is separate. However, it omits auth requirements (except for hard delete), rate limits, or other side effects. Adequate but not thorough.

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 sentences that front-load the main purpose and then provide specific behavioral notes. No redundant or extra information. Every sentence adds value.

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?

Given no output schema, the description does not explain return values. It covers key behaviors but does not elaborate on parameters like 'GitHub linkage' or 'metadata' merging behavior. With 7 parameters and low schema coverage, slightly more detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (29% only for 'metadata' and 'restore'). The description adds meaning by explaining that 'status'='archived' triggers soft-delete and that 'restore' is required for un-archiving. It also implies atomicity across all properties. This compensates for the schema gaps.

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

Purpose5/5

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

The description clearly states 'Edit any plan property atomically' and lists specific properties. It distinguishes this tool from 'delete_plan' by noting soft-delete via status='archived' versus hard delete via REST-only endpoint, providing clear differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives explicit guidance on when to use this tool (editing plan properties) and when not (hard delete requires REST-only admin auth). It also explains the restore flag for un-archiving. However, it does not compare with sibling tools that update other resources, which is acceptable given they target different entities.

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