Skip to main content
Glama
n24q02m

Better Godot MCP

by n24q02m

nodes

Destructive

Manage scene nodes in Godot by adding, removing, renaming, listing, and setting or getting properties using node paths relative to scene root.

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
nameNoNode name
typeNoNode type (for add, default: Node)
valueNoProperty value (for set_property)
actionYesAction to perform
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)
scene_pathNoPath to scene file
project_pathNoPath to Godot project directory

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already set destructiveHint=true; description lists destructive actions (remove, set_property) but does not elaborate on consequences or irreversibility beyond what annotations imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with an action list and note on paths, but could be slightly more concise by avoiding repetition of parameter names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers actions and parameters adequately, but lacks description of return values (e.g., what 'list' returns) despite an output schema existing; still sufficient for basic usage.

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?

Description adds value beyond schema by providing default values (type='Node', parent='.') and clarifies node path conventions, despite 100% schema coverage.

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 manages scene node operations with explicit actions (add, remove, rename, etc.), distinguishing it from sibling tools focusing on other domains like animation or audio.

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?

Description provides structured format for actions with required/optional params and explains node path syntax, but does not explicitly state when to use this tool versus alternatives or specify exclusions.

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