Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

batch_add_nodes

Add multiple nodes to a Godot scene in one call, so you can build or update scene trees without repetitive single-node edits.

Instructions

Add multiple nodes to the scene in a single call.

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": {
      "nodes": "<nodes>"
    },
    "name": "batch_add_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesArray of node descriptors

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a mutation tool and largely fails it. It does not say whether the batch is atomic (all-or-nothing) or partially applied on failure, how parent_path resolution or ordering works, or what happens to nodes whose parent does not exist.

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?

A single front-loaded sentence with no filler; the batching cue arrives early and every word earns its place. Its brevity is efficient rather than padded, though it leaves the definition thin overall.

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?

For a mutation tool with no annotations and no output schema, an agent still needs to know failure semantics (atomic vs partial), whether created nodes are returned or must be looked up, and any batch-size constraints. None of that is present.

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% and there is only one parameter, so the schema already documents the node array and its fields. The description adds no meaning about descriptor contents, defaults, or parent_path semantics, which is the baseline-3 outcome when the schema does the work.

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 specific verb and resource ('Add multiple nodes to the scene') and the phrase 'in a single call' distinguishes it from the singular add_node sibling. It stops short of explicitly naming alternatives, but an agent can tell what this does.

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?

'In a single call' implies the batching rationale versus repeated add_node calls, which is useful implied guidance. There is no explicit when-to-use/when-not statement, no mention of limits on batch size, and no note on when to prefer the singular tool.

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