Skip to main content
Glama

scene-node-add

Add any Godot node type to an existing scene and configure properties via JSON. Replaces specialized create node tools.

Instructions

[compact alias of add_node] Adds ANY node type to an existing scene. This is the universal node creation tool — replaces all specialized create_* node tools. Supports ALL ClassDB node types (Camera3D, DirectionalLight3D, AudioStreamPlayer, HTTPRequest, RayCast3D, etc.). Set any property via the properties parameter with type conversion support (Vector2, Vector3, Color, etc.). Use query_classes to discover available node types. Use query_class_info to discover available properties for a type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesAbsolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.
scenePathYesPath to .tscn file relative to project (e.g., "scenes/Player.tscn")
parentNodePathNoNode path within scene (e.g., "." for root, "Player" for direct child, "Player/Sprite2D" for nested)
nodeTypeYesGodot node class name (e.g., "Sprite2D", "CollisionShape2D", "CharacterBody2D"). Must be valid Godot 4 class.
nodeNameYesName for the new node (will be unique identifier in scene tree)
propertiesNoOptional properties to set on the node (as JSON string). Tagged Godot values such as {"position":{"type":"Vector2","x":100,"y":200}} are the most explicit form; common typed properties like Vector2 also accept inferred shapes such as {"position":{"x":100,"y":200}} or {"position":[100,200]}.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses support for all node types, property setting with type conversion, but omits side effects like requiring scene save or editor updates.

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?

Compact, no wasted words. Front-loaded with purpose and key differentiators. Every sentence adds value.

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?

Covers purpose, usage, property format, and discovery tools. With no output schema or annotations, description provides sufficient context for a node addition tool.

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%, but description adds meaning beyond schema by explaining type conversion for properties and the format for parentNodePath. Provides concrete examples for property inference shapes.

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?

Description clearly states it adds ANY node type to an existing scene and is a universal replacement for specialized create_* tools. It distinguishes itself from sibling tools like scene-node-delete and scene-node-set.

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?

Explicitly says to use this instead of specialized create_* tools and suggests using query_classes and query_class_info for discovery. Does not explicitly state when not to use, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wvfp/Gear-Godot-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server