Skip to main content
Glama

add_node

Add a node to a Godot scene with automatic saving. Set position, rotation, scale, visibility, and custom properties directly.

Instructions

Add a node to a Godot scene. Saves automatically. Common spatial properties (position, position3d, rotation, scale, visible, modulate) can be set as top-level params; for any other property, pass it under properties. Vector2/Vector3/Color values auto-convert from {x,y}/{x,y,z}/{r,g,b,a}. parentNodePath defaults to the scene root. Errors if nodeType is not a registered Godot class or parentNodePath does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory
scenePathYesScene file path relative to the project
nodeTypeYesGodot node class to instantiate (e.g. "Sprite2D", "CollisionShape2D", "Label")
nodeNameYesName for the new node as it appears in the scene tree
parentNodePathNoParent node path from scene root (e.g. "root/Player"). Defaults to the root node.
positionNoVector2 position (e.g. {"x": 100, "y": 200})
position3dNoVector3 position for 3D nodes (e.g. {"x": 0, "y": 1, "z": 0})
rotationNoRotation in radians
scaleNoVector2 scale (e.g. {"x": 2, "y": 2})
visibleNoWhether the node is visible
modulateNoColor modulation (e.g. {"r": 1, "g": 0, "b": 0, "a": 1})
propertiesNoAdditional property values as a JSON object. Top-level params (position, rotation, etc.) take precedence over keys in this dict.
Behavior4/5

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

The description discloses that saving is automatic (mutation), auto-conversion for Vector2/Vector3/Color values, and precedence of top-level params over properties. It also mentions error conditions. Since no annotations are provided, the description carries the full burden, and it covers key behavioral traits without contradictions.

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 concise (4 sentences), front-loads the purpose, and every sentence adds necessary information. There is no redundancy or filler.

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?

Given the 12 parameters, nested objects, and lack of output schema/annotations, the description covers the main points: purpose, auto-save, parameter usage, auto-conversion, defaults, and errors. It could mention the return value, but overall it provides sufficient context for an agent to use the tool correctly.

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?

The schema has 100% coverage, but the description adds significant value by explaining the pattern: common spatial properties as top-level params, others via 'properties', and auto-conversion. It also clarifies the default for parentNodePath. This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description clearly states the action ('Add a node') and the resource ('to a Godot scene'), and mentions common spatial properties. It distinguishes the basic purpose, but does not explicitly differentiate from sibling tools like duplicate_node or batch_scene_operations, which could confuse an agent about when to use this tool.

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 provides constraints: default parentNodePath, error conditions for nodeType and parentNodePath. However, it offers no guidance on when to use this tool vs. alternatives such as batch_scene_operations or duplicate_node, leaving the agent to infer usage context.

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/Erodenn/godot-mcp-runtime'

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