Planning System MCP Server

move_node

Move a plan node to a new parent within the same plan, ensuring no cycles are created. Optionally specify the position among siblings.

Instructions

Reparent a node within the same plan. Cycle-safe (server rejects moves that would create a tree cycle). Optional position sets the order_index among siblings.

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": {
      "node_id": "<node_id>",
      "new_parent_id": "<new_parent_id>"
    },
    "name": "move_node"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes
`new_parent_id`	Yes
`plan_id`	No	Auto-resolved if omitted.
`position`	No	Optional order_index among siblings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.8.1Apr 29, 2026

addedInput schema / properties / new_parent_id
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / node_id / description
```
Removed value: -"Node ID to move"
```

removedInput schema / properties / order_index

Removed value: -{
-  "description": "New position index",
-  "type": "integer"
-}

removedInput schema / properties / parent_id

Removed value: -{
-  "description": "New parent node ID",
-  "type": "string"
-}

changedInput schema / properties / plan_id / description

Previous value: -"Plan ID"New value: +"Auto-resolved if omitted."

addedInput schema / properties / position

Added value: +{
+  "description": "Optional order_index among siblings.",
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "plan_id",
-  "node_id"
-]New value: +[
+  "node_id",
+  "new_parent_id"
+]

First observedDec 29, 2025

TDQS

A3.9/5.0

Behavior4/5

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

The description discloses that the tool is cycle-safe, meaning the server rejects cycles, and mentions optional position setting. This adds value beyond the absence of annotations, though it does not cover authorization or side effects.

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 concise, front-loaded sentences cover the core purpose, cycle-safety, and optional parameter. No wasted words.

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?

Given no output schema, the description adequately covers key behaviors (reparenting, cycle-safety, position). Missing return value specification, but overall sufficient for a move tool.

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

Parameters2/5

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

Schema coverage is 50% (plan_id and position have descriptions). The description clarifies 'position' as order_index and implies plan_id is auto-resolved, but adds nothing for node_id or new_parent_id beyond obvious naming.

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 uses a specific verb 'Reparent' and resource 'node within the same plan', clearly distinguishing it from siblings like delete_node, update_node, etc.

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?

While the description mentions cycle-safety and optional position, it lacks explicit guidance on when to use this tool versus alternatives like update_node or when not to use it. The context is implied but not fully directive.

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