cognigy-ai-mcp-management-server

move_node

Repositions a node in a flow relative to a target node, with a dry run option to validate before moving.

Instructions

Moves a node to a new position in a Cognigy.AI flow. MUTATING: This reorganizes the flow structure. Use dryRun=true (default) to validate first. Moving nodes affects execution order.

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": {
      "flowId": "<flowId>",
      "nodeId": "<nodeId>",
      "targetNodeId": "<targetNodeId>",
      "mode": "<mode>"
    },
    "name": "move_node"
  }
}

Input Schema

Name	Required	Description
`mode`	Yes	How to position relative to target: append (as next sibling), prepend (as previous sibling), insertChildAt (as child at position), insertAfter, insertBefore
`dryRun`	No	If true (default), validates the operation without moving. Set to false to actually move the node.
`flowId`	Yes	The flow ID containing the node
`nodeId`	Yes	The ID of the node to move
`position`	No	Position index when using insertChildAt mode
`targetNodeId`	Yes	The ID of the target node to move relative to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Description explicitly says 'MUTATING' and explains that it reorganizes flow structure and affects execution order. Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description adds value by detailing side effects and the dryRun safety mechanism. Could mention reversibility but overall strong.

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?

Three sentences: purpose, mutation warning, usage guidance. Front-loaded with key information, no unnecessary words. Excellent conciseness.

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?

For a mutation tool with 6 parameters and no output schema, the description covers purpose, side effects (execution order), and validation guidance (dryRun). Could mention expected result or confirmation, but overall adequate.

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 coverage is 100% and the description adds little beyond what the schema provides. It emphasizes dryRun and its default, but all parameter details are already in the input schema. Baseline 3 is appropriate.

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 the action: 'Moves a node to a new position in a Cognigy.AI flow.' This is a specific verb-resource pair. Among siblings like create_node, update_node, delete_node, move_node is uniquely identified.

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 advises using dryRun=true to validate first and notes that moving nodes affects execution order. This gives clear context on when to use. However, it does not explicitly state when to avoid this tool or suggest alternatives like update_node for property changes.

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

Deploy Server