Skip to main content
Glama

nodes

Destructive

Manage scene nodes: add, remove, rename, list, and modify properties in Godot 4.x scenes.

Instructions

Scene node operations.

Actions (required params -> optional):

  • add (scene_path, name -> type="Node", parent=".", project_path)

  • remove (scene_path, name -> project_path)

  • rename (scene_path, name, new_name -> project_path)

  • list (scene_path -> project_path)

  • set_property (scene_path, name, property, value -> project_path)

  • get_property (scene_path, name, property -> project_path)

Node paths: relative to scene root using "/" (e.g., "Player/Sprite2D"). Use "." for root.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
project_pathNoPath to Godot project directory
scene_pathNoPath to scene file
nameNoNode name
typeNoNode type (for add, default: Node)
parentNoParent node path relative to scene root (for add, default: "." = root). Use "/" separator, e.g., "Player/Sprite2D"
new_nameNoNew name (for rename)
propertyNoProperty name (for get/set_property)
valueNoProperty value (for set_property)
Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description confirms mutability through actions like add/remove/rename. It adds context on node path format but could mention persistence or undo behavior.

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, using a clear action-param list format and front-loading the purpose. Every sentence is essential and well-organized.

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 all actions, params, and node path conventions. Missing example property values or return format, but given no output schema and 9 params, it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds significant value by mapping actions to their required/optional params and providing defaults (e.g., 'type' default 'Node' for add, parent default '.').

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 'Scene node operations' and lists specific actions (add, remove, rename, list, set/get property), making it distinct from sibling tools like 'animation' or 'scripts'.

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?

Provides a structured list of actions with required and optional parameters, along with node path syntax. However, it does not explicitly contrast with sibling tools or mention when not to use this tool.

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/n24q02m/better-godot-mcp'

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