Skip to main content
Glama

Rename everywhere

godot_rename
Destructive

Rename GDScript symbols, scene nodes, groups, input actions, autoloads, or project settings across a Godot project, or move res:// files and update all references; preview before writing.

Instructions

Rename a function, signal, variable, class_name, autoload, input action, group or node name everywhere it is used (GDScript, scene connections, node paths, groups, project settings), or move a res:// file together with its .uid and .import files and every reference to it. from and to are both names or both res:// paths. Without write it changes nothing and returns the exact lines it would change and what it could not change; with write: true it applies them and reports the review errors before and after (an error result when there are more after). Refuses, with an error, when the new name is already taken. Call godot_usages first to see what it will touch. For a setting value, an input event or a node property, use godot_project_edit or godot_scene_edit instead.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "godot_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesthe new name, or the new res:// path
fromYesthe current name, or a res:// path
pathNoproject folder, or a file or folder inside it (relative to the server's folder; default: the current project)
writeNoapply the rename (default false: show the plan only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / path / description
      Previous value: -"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."New value: +"project folder, or a file or folder inside it (relative to the server's folder; default: the current project)"
  2. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / path / description
      Previous value: -"Project directory or a path inside it (default: the current project)."New value: +"The project folder, or any file or folder inside it (Godotwright walks up to project.godot). Relative paths start at the server's folder. Default: the current project."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that without `write` nothing changes and the exact lines that would change are returned, that with `write: true` it reports review errors before and after (with an error result on regression), and that it refuses with an error when the new name is already taken. These details are consistent with destructiveHint=true and idempotentHint=false and add real operational context the annotation cannot convey.

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?

Front-loads the rename scope, then the dry-run/apply contract, then the exclusions – a sensible order with no filler sentences. The opening enumeration is dense with parenthetical asides, which slightly slows parsing but every element is substantive.

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

Completeness5/5

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

For a destructive, multi-target rename tool with no output schema, the description covers the preview-vs-apply contract, what failure looks like, the collision refusal, and where the agent should go for non-rename edits. Nothing essential to calling it safely is missing.

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

Parameters4/5

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

Schema coverage is 100% so each parameter is already documented, but the description adds the cross-parameter constraint that `from` and `to` must both be names or both be res:// paths, which the schema does not express. The dry-run/apply meaning of `write` is reinforced rather than newly introduced, keeping it just short of a 5.

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?

States the specific verb (rename) plus an enumerated set of resources (function, signal, variable, class_name, autoload, input action, group, node name, res:// file with .uid/.import), so the agent knows exactly what scope of change is covered. It is also clearly separable from siblings because it names the tools to use for setting values, input events and node properties.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: 'Call godot_usages first to see what it will touch' and 'For a setting value, an input event or a node property, use godot_project_edit or godot_scene_edit instead.' The dry-run-then-write workflow is spelled out, which is the key when-to-use decision for a destructive tool.

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