Skip to main content
Glama

add_node

Add a node to a Godot scene and save automatically. Set position, rotation, scale, visibility, and other properties via simple parameters.

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. Returns a plain-text confirmation message naming the new node and type. 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.
Behavior5/5

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

With no annotations, the description must fully convey behavior. It covers automatic saving, parameter precedence (top-level vs. properties), auto-conversion of Vector2/Vector3/Color, default parentNodePath, return format (plain-text confirmation), and error conditions (invalid nodeType or missing parent). This is thorough and leaves little ambiguity.

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 extremely concise—three sentences covering purpose, key behaviors, defaults, and error conditions. Every sentence serves a distinct purpose without redundancy. It is front-loaded with the core action and essential details.

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 tool's complexity (12 parameters, nested objects, no output schema), the description provides adequate context: behavior, defaults, auto-conversion, return type, and errors. It is slightly incomplete in not explaining when to use this vs. other tools, but within its scope it is solid. The lack of output schema is compensated by describing the return format.

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?

Although the schema already covers 100% of parameters, the description adds meaningful context: which parameters are 'common spatial properties,' how properties dict works as a catch-all, auto-conversion format rules, and default behavior for parentNodePath. This goes beyond simple 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 main action (add a node to a Godot scene) and mentions automatic saving. However, it does not explicitly differentiate from sibling tools like duplicate_node or batch_scene_operations, leaving some ambiguity about when to choose this tool over others.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., duplicate_node, batch_scene_operations). The description omits any when-to-use or when-not-to-use information, which is a significant gap given the numerous sibling tools.

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