Skip to main content
Glama

Node Create

node_create

Create a new Godot scene tree node by class type or instantiate a PackedScene under a specified parent, so AI assistants can build and extend scenes in the live editor.

Instructions

Create (spawn) a new node in the scene tree.

Creates a node of the given type and adds it to the parent, or instantiates a PackedScene from scene_path. type and scene_path are mutually exclusive — when scene_path is given, type is ignored.

Creating below an instance's internal nodes requires Editable Children to be enabled in Godot. Attaching directly to its root is supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "node_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name; Godot auto-names if empty.
typeNoGodot node class (e.g. "Node3D", "MeshInstance3D").
scene_fileNoOptional editor-scene guard (EDITED_SCENE_MISMATCH).
scene_pathNoOptional res:// path of a PackedScene to instantiate.
session_idNoOptional Godot session to target. Empty = active session.
parent_pathNoParent path relative to the edited scene root (e.g. "/Main"), NOT runtime "/root/...". Empty = scene root.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.4
  2. Removedv3.0.7
  3. First observedv2.9.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: mutual exclusivity with precedence, a Godot-specific constraint around instance internals, and the sanctioned exception of attaching at the instance root. It omits whether the operation is undoable and what happens on name collisions or invalid types, which would be valuable for a mutating tool.

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?

Short and front-loaded: purpose in the first sentence, then the two-mode behavior, then the Godot-specific constraint. No redundant restatement of the title or schema fields.

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?

Parameters are fully documented in the schema and an output schema exists, so the description only needs to cover behavior—which it largely does for a creation tool with two modes. Minor gaps remain: no mention of undo semantics, failure modes, or how the new node's path/name is returned by reference.

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 the baseline is 3. The description adds real semantics beyond the schema by explaining the interaction between type and scene_path (precedence), which the per-parameter descriptions do not convey. Other parameters (parent_path, scene_file, session_id, name) are left entirely to the schema.

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 a specific verb and resource ('Create (spawn) a new node in the scene tree') and immediately covers both modes of creation (by type or by PackedScene instantiation). This clearly separates it from siblings like node_set_property or node_manage, which do not create nodes.

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?

Gives the key selection rule between the two creation modes ('type and scene_path are mutually exclusive — when scene_path is given, type is ignored') and a precondition for nested instantiation (Editable Children). It does not point to a sibling for alternative operations, but the when-to-use context for this tool is clear.

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