Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_node

Adds a new node of a specified Godot class to the currently open scene, with optional parent path, name, and initial properties.

Instructions

Add a new node to the currently open scene.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "add_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the new node
typeYesGodot node class (e.g. Sprite2D, MeshInstance3D)
propertiesNoInitial property values to set on the node
parent_pathNoPath of the parent node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only establishes that this is a mutation on the active scene. It does not say what happens if parent_path is omitted, whether the add is undoable, whether properties are applied before or after the node enters the tree, or what is returned (e.g., the new node's path).

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?

One short sentence with the operation and its scope front-loaded and no filler. It is efficient rather than padded, though the brevity comes at the cost of the missing guidance noted elsewhere.

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

Completeness2/5

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

This is a mutation tool with no annotations, a nested-object parameter, and no output schema, so the description should do real work. As written it omits parent-path defaults, property application semantics, and any return value, leaving the agent to guess at the most error-prone parts of the call.

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

Parameters3/5

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

Schema description coverage is 100%, so each of the four parameters is already documented in the schema, which sets the baseline at 3. The description adds no parameter-level meaning beyond that, and notably leaves the nested `properties` object and the default parent behavior unexplained.

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 gives a clear verb and resource ("Add a new node") plus scope ("to the currently open scene"), so the agent knows exactly what operation this is. It does not distinguish itself from the sibling batch_add_nodes, which performs a superficially similar action, so it falls short of a 5.

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?

It never states when to prefer this tool over batch_add_nodes or add_scene_instance, nor does it state prerequisites such as a scene needing to be open. The only guidance available is the implicit read of the name.

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

Deploy Server

Other Tools