Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

move_node

Reparent a node to a new parent in the Godot scene tree by specifying the node path and target parent path.

Instructions

Reparent a node to a different parent in the scene tree.

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_path": "<node_path>",
      "new_parent_path": "<new_parent_path>"
    },
    "name": "move_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the node to move
new_parent_pathYesPath of the new parent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only states the mutation. It does not say whether the node's children and signals move with it, whether the local transform is preserved, what happens if the new parent is a descendant of the node, or what errors look like.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity leaves the reader with nothing on failure modes or transform handling.

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?

The tool is structurally simple (two required string params, no nested objects, no output schema), but as a mutation with no annotations and no output schema the description should cover reparenting side effects and failure conditions. Those gaps are what an agent most needs before calling it.

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 both properties are already documented as 'Path of the node to move' and 'Path of the new parent'. The description adds no path-format detail (absolute vs relative, node path syntax) or constraint such as the two paths being distinct.

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 verb ('Reparent') and resource ('a node') plus the target state ('a different parent in the scene tree'), which is far clearer than a bare 'move'. It does not, however, distinguish itself from sibling operations that also relocate or reassign nodes, such as move_file or set_node_owner.

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?

There is no when-to-use guidance, no precondition (e.g. that both nodes must exist or belong to the same scene), and no pointer to alternatives such as duplicate_node plus delete_node. The agent must infer the call context entirely on its own.

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

Deploy Server

Other Tools