Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

rename_node

Rename a node in the scene tree by specifying its path and new name, enabling quick updates to Godot scene structure.

Instructions

Rename a node in the scene.

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_name": "<new_name>"
    },
    "name": "rename_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameYesNew name
node_pathYesPath of the node to rename

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?

With no annotations, the description bears the full disclosure burden. It implies a mutation but says nothing about permissions, whether the rename is reversible, what happens on name collision or invalid characters, or what occurs if node_path does not resolve — all material for a write operation.

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 zero filler — appropriately sized for a two-parameter tool. It is efficient but so terse that its brevity shades into under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-required-parameter tool with full schema coverage, the description is minimally sufficient to call it. However, the absence of annotations and output schema means error behavior and result semantics remain entirely undisclosed.

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 (node_path, new_name) are documented in the schema itself. The description adds no format details beyond it, which meets the baseline of 3 but no more.

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?

"Rename a node in the scene" gives a specific verb (rename) and resource (node) with the operational scope (in the scene). It is clear enough to distinguish from sibling mutations like replace_node_type or set_node_owner, though it never explicitly contrasts with them.

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 gives no guidance on when to use this versus alternatives, no preconditions (e.g., node must exist, name must be unique or valid), and no exclusions. Usage must be inferred entirely from the tool name.

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