Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

replace_node_type

Replaces a Godot node with a different type while preserving its children and position, enabling quick node type changes without rebuilding the scene subtree.

Instructions

Replace a node with a new node of a different type (preserving children and position).

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_type": "<new_type>"
    },
    "name": "replace_node_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_typeYesGodot class to replace it with
node_pathYesPath of the node to replace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two meaningful behavioral traits: children and position are preserved. It does not mention whether existing property values, scripts, or signals survive the type change, nor whether the operation is reversible or what errors occur on an invalid Godot class.

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?

One sentence, front-loaded with the action and immediately followed by the most decision-relevant detail (preserved children and position). No filler or redundancy.

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 two-parameter mutation with no output schema, the definition covers the essential behavior an agent needs before calling. The remaining gap — what happens to the old node's properties and script when the type changes — is notable but not disqualifying for a tool of this simplicity.

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%, so both parameters are already documented in the schema, and the description adds essentially no additional semantics about the path format or the acceptable class names. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Replace a node') plus the key qualifier 'with a new node of a different type', which cleanly separates it from add_node, delete_node, or duplicate_node. It is clear what operation is performed, though it does not name a sibling alternative explicitly.

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?

Usage is implied by the operation itself — an agent would choose this when it needs to change a node's class in place rather than removing and re-adding it. There is no explicit when-to-use or when-not-to-use guidance, and no stated prerequisites (e.g., that the node must exist at node_path).

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