Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

rename_node

Rename a node in the open Godot scene and update every relative NodePath through it in the same undo step, rejecting conflicting names and listing affected paths.

Instructions

Rename a node in the open scene (undoable). Like the Scene dock, it also respells every relative NodePath in the scene that leads through the node (an exported NodePath, Array[NodePath] or Dictionary entries, RemoteTransform3D.remote_path, a %unique path) in the same undo step, and the reply lists them. It refuses a sibling's name, and a %unique name that another node already holds. Characters a node name cannot hold are replaced the way Godot replaces them, and the reply gives the name the node ended up with.

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": {
      "target": "<target>",
      "name": "<name>"
    },
    "name": "rename_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.1
  2. Removedv1.10.0
  3. First observedv1.0.0

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavior: it is undoable, respells relative NodePaths (including exported NodePaths, arrays, dictionaries, RemoteTransform3D paths, and %unique paths) in the same undo step, lists affected paths in the reply, refuses certain names, sanitizes invalid characters, and reports the final name. These details give the agent a rich understanding of side effects and validation.

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?

The purpose is front-loaded in the first sentence, and the remaining clauses add useful behavioral detail without obvious filler. The description is dense but appropriately sized for a mutation tool with complex side effects.

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 rename tool with no output schema, the description covers undo behavior, NodePath updates, conflict refusals, name sanitization, and reply contents. The main gap is the unexplained 'target' parameter, but overall the agent has enough context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies name semantics somewhat by discussing sibling-name refusal, uniqueness rules, invalid-character replacement, and the final name in the reply, but it does not explain the 'target' parameter at all—whether it is a node path, node reference, or something else.

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 opens with a specific verb and resource: 'Rename a node in the open scene (undoable).' It clearly distinguishes renaming from creation, deletion, movement, or reparenting, though it does not explicitly name sibling tools as alternatives.

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 'Rename a node in the open scene,' and the description adds refusal conditions such as sibling-name conflicts and duplicate unique names. However, it does not explicitly state when to use this tool versus siblings like move_node, reparent_node, or set_property.

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