Godot MCP

Overview Schema Source Related Servers Discussions Admin

godot_edit_scene

Modify existing nodes in Godot scenes by updating transforms, renaming, reparenting, or deleting them to edit game objects and structure.

Instructions

Modify an existing node in a saved scene by updating its transform, renaming it, reparenting it, or deleting it.

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": {
      "project_path": "<project_path>",
      "scene_path": "<scene_path>"
    },
    "name": "godot_edit_scene"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	Path to the Godot project directory or its project.godot file.
`scene_path`	Yes	Path to the target .tscn file. Absolute, relative, and res:// paths are supported.
`node_path`	No	Scene-relative node path to edit. Use '.' for the root node.	.
`transform`	No	Optional transform fields to update. Vector values can be passed as objects like {x, y} or {x, y, z}.
`new_name`	No	Optional new name for the target node.
`new_parent_path`	No	Optional new scene-relative parent path for the target node. Use '.' for the root.
`delete`	No	Delete the target node. This cannot be combined with other edits.
`godot_executable`	No	Optional explicit path to the Godot executable or .app bundle.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 22, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool can 'delete' nodes, implying destructive behavior, but doesn't specify if changes are reversible, what permissions are needed, or how errors are handled. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that front-loads the core purpose and enumerates the key actions without any wasted words. Every part of the sentence directly contributes to understanding the tool's functionality.

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?

Given the tool's complexity (8 parameters, mutation operations, no annotations, no output schema), the description is adequate but incomplete. It covers the purpose and scope well, but lacks details on behavioral traits like error handling, side effects, or return values, which are crucial for a tool that modifies scene data.

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?

The schema description coverage is 100%, so the schema already documents all 8 parameters thoroughly. The description adds minimal value beyond the schema by listing the types of modifications (transform, rename, reparent, delete), which loosely maps to some parameters, but doesn't provide additional syntax or format details. Baseline 3 is appropriate 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Modify an existing node'), the resource ('in a saved scene'), and the scope of modifications ('updating its transform, renaming it, reparenting it, or deleting it'). It distinguishes itself from siblings like godot_add_node (adds new nodes) and godot_update_node_transform (only updates transform).

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

Usage Guidelines4/5

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

The description implies usage context by specifying it's for modifying 'an existing node in a saved scene,' which helps differentiate from creation tools. However, it doesn't explicitly state when NOT to use it or name specific alternatives like godot_update_node_transform for transform-only updates, leaving some ambiguity.

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