Godot MCP

Overview Schema Source Related Servers Discussions Admin

godot_add_node

Add a new node to an existing Godot scene by specifying the node type, scene path, and parent location within the project.

Instructions

Add a new node of any instantiable Godot node type to an existing saved 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": {
      "project_path": "<project_path>",
      "scene_path": "<scene_path>",
      "node_type": "<node_type>"
    },
    "name": "godot_add_node"
  }
}

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_type`	Yes	Godot node class to instantiate, such as Sprite2D, Timer, Control, or AudioStreamPlayer2D.
`parent_path`	No	Scene-relative node path where the new node should be attached. Use '.' for the root.	.
`node_name`	No	Optional explicit node name. Defaults to the chosen node type.
`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

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a write operation ('Add'), it doesn't mention important behavioral traits like whether this requires specific permissions, if changes are saved immediately, potential side effects on scene structure, or error conditions. The description is minimal and lacks operational context.

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 communicates the core purpose without unnecessary words. It's appropriately sized for the tool's complexity and gets straight to the point with zero waste.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after node addition, potential return values, error conditions, or important behavioral constraints. Given the tool modifies scene files and has 6 parameters, more operational context would be needed for an agent to use it effectively.

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 all parameters are documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. It mentions 'any instantiable Godot node type' which aligns with the node_type parameter but doesn't provide additional semantic context.

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 ('Add a new node'), the resource type ('any instantiable Godot node type'), and the target location ('to an existing saved scene'). It distinguishes itself from siblings like godot_create_scene (creates new scenes) and godot_edit_scene (general scene editing).

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?

The description implies usage context by specifying 'existing saved scene,' suggesting this tool is for modifying scenes rather than creating them. However, it doesn't explicitly state when to use this versus alternatives like godot_edit_scene or provide clear exclusions for when other tools would be more appropriate.

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