Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_scene_instance

Instance an existing Godot scene into the currently open scene, with optional parent node and instance name, to add reusable scene nodes without manual editor steps.

Instructions

Instance an existing scene into 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": {
      "scene_path": "<scene_path>"
    },
    "name": "add_scene_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the instanced node
scene_pathYesres:// path to the scene to instance
parent_pathNoNode path of the parent (default: root)

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 provided, so the description carries the full behavioral burden. It does not say what happens on name collisions, whether the change is persisted/saved, whether the instanced node is returned, or any error conditions for an invalid res:// 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?

A single efficient sentence with the action and scope front-loaded and no wasted wording. It is arguably too terse for a mutation tool, but nothing is redundant.

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 3-parameter mutation tool with no annotations and no output schema, the definition should mention the return value (e.g., the created node path) and at least one failure mode. Neither is covered, leaving meaningful gaps.

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 all three parameters are already documented in the schema. The description adds nothing about parameter meaning beyond confirming the target is the open scene, so baseline 3 applies.

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?

States a specific verb ('Instance') and resource ('an existing scene') with clear scope ('into the currently open scene'). An agent can distinguish it from create_scene or open_scene, though the description never names those siblings explicitly.

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?

Usage is only implied: the phrase 'currently open scene' signals a precondition that a scene must already be open, but there is no explicit guidance on when to use this versus add_mesh_instance, create_scene, or other alternatives.

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