Skip to main content
Glama
TAgents

Planning System MCP Server

by TAgents

move_node

Reposition tasks or phases within hierarchical project plans by changing parent nodes or adjusting order positions to maintain organized workflows.

Instructions

Move a node to a different parent or position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plan_idYesPlan ID
node_idYesNode ID to move
parent_idNoNew parent node ID
order_indexNoNew position index

Implementation Reference

  • Handler for move_node tool: Posts to dedicated move endpoint or falls back to updating parent_id and order_index on the node
    if (name === "move_node") {
      const { plan_id, node_id, parent_id, order_index } = args;
      
      try {
        // Call the move endpoint - using POST as per API definition
        const response = await apiClient.axiosInstance.post(
          `/plans/${plan_id}/nodes/${node_id}/move`,
          { 
            parent_id: parent_id || null,
            order_index: order_index !== undefined ? order_index : null
          }
        );
        
        return formatResponse(response.data);
      } catch (error) {
        // If endpoint still doesn't work, try updating the node directly
        if (error.response && error.response.status === 404) {
          console.error('Move endpoint not found, trying direct update');
          // Fallback to updating the node's parent_id via regular update
          const updateResponse = await apiClient.nodes.updateNode(plan_id, node_id, {
            parent_id: parent_id || null,
            order_index: order_index !== undefined ? order_index : null
          });
          return formatResponse(updateResponse);
        }
        throw error;
      }
    }
  • src/tools.js:236-249 (registration)
    Registration of move_node tool in the tools list, including input schema definition
    {
      name: "move_node",
      description: "Move a node to a different parent or position",
      inputSchema: {
        type: "object",
        properties: {
          plan_id: { type: "string", description: "Plan ID" },
          node_id: { type: "string", description: "Node ID to move" },
          parent_id: { type: "string", description: "New parent node ID" },
          order_index: { type: "integer", description: "New position index" }
        },
        required: ["plan_id", "node_id"]
      }
    },
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 of behavioral disclosure. It states the action ('Move') but doesn't cover critical traits: whether it's destructive (likely yes, as it modifies node relationships), permission requirements, error handling (e.g., invalid IDs), or side effects (e.g., impact on child nodes). This leaves significant gaps for safe and effective use.

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?

The description is a single, efficient sentence that front-loads the core action ('Move a node') and specifies the target ('to a different parent or position'). There is no wasted wording, repetition, or unnecessary detail, making it highly concise and well-structured for quick comprehension.

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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., destructiveness, permissions), usage context, and return values. While the schema covers parameters well, the overall context for safe and correct invocation is insufficient, especially compared to siblings that might handle similar operations.

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 clear parameter descriptions in the schema (e.g., 'Plan ID', 'Node ID to move'). The description adds minimal value beyond the schema, only implying that 'parent_id' and 'order_index' relate to repositioning. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding.

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 clearly states the action ('Move') and resource ('a node'), specifying the operation as repositioning within a hierarchy ('to a different parent or position'). It distinguishes from siblings like 'create_node' or 'delete_node' by focusing on relocation rather than creation or removal. However, it doesn't explicitly differentiate from 'update_node' or 'batch_update_nodes', which might also handle positional changes, leaving some ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a plan or existing nodes), exclusions (e.g., not for moving between plans), or comparisons to siblings like 'update_node' for other modifications. Without such context, an agent might misuse it or overlook better options.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TAgents/agent-planner-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server