Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_spawn_node

Creates a new Godot runtime node of any specified type, with optional name, parent path, and properties, so AI assistants can add scene objects during live game control.

Instructions

Create a new node of any type at runtime

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": "game_spawn_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the new node. Default: auto-generated
typeYesNode class name (e.g. "Sprite2D", "CharacterBody3D")
parentPathNoParent node path. Default: "/root"
propertiesNoProperties to set on the new node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the core action and runtime context but omits side effects such as the node entering the scene tree, lifecycle callbacks, ownership, return values, or prerequisites.

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?

The description is a single, front-loaded sentence with no filler. It is concise and readable, though it could be slightly more informative without becoming bloated.

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 runtime mutation tool with no annotations and no output schema, this is under-specified. Missing context includes what the tool returns, whether the game must already be running, and how the new node is integrated into the scene tree.

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 the baseline is 3. The description adds only the generic 'any type' emphasis and does not meaningfully extend the parameter information already present in the schema.

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 the verb 'Create', the resource 'node', and the scope 'any type at runtime'. This distinguishes it from scene-editing tools like add_node and from instantiation tools like game_instantiate_scene.

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?

The phrase 'at runtime' implies this is for dynamic node creation during a running game, but the description does not explicitly name alternatives or state when not to use it. With many sibling tools, more routing guidance would help.

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