godot-mcp-extended

Overview Schema Source Related Servers Discussions Admin

instance_scene

Instances a source .tscn into a target scene under a parent node, enabling reusable scene composition in Godot projects.

Instructions

Instance a source .tscn into another scene under a parent node

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>",
      "parentNodePath": "<parentNodePath>",
      "sourceScene": "<sourceScene>"
    },
    "name": "instance_scene"
  }
}

Input Schema

Name	Required	Description
`nodeName`	No	Optional name for the instance
`scenePath`	Yes	Target scene file relative to project
`projectPath`	Yes	Path to the Godot project directory
`sourceScene`	Yes	Source .tscn path relative to project
`parentNodePath`	Yes	Parent path like root or root/Level

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 19, 2026

TDQS

C2.9/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, yet it says nothing about side effects: whether the target scene is written to disk or only modified in memory, whether an open editor is required, or what happens on invalid paths. Only the bare mutation intent is conveyed.

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, and the source-to-target relationship is stated up front. It is efficient, though extremely terse for a five-parameter mutation tool.

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 five-parameter mutating tool with no annotations and no output schema, the definition omits persistence/save behavior, error cases, and the meaning of an omitted nodeName. The schema covers inputs, but an agent still lacks the behavioral context needed to call this confidently.

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 five parameters including sourceScene, scenePath, and parentNodePath are already documented. The description adds no extra semantics such as defaulting behavior for nodeName or path format beyond what the schema states.

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') with a clear resource pair: a source .tscn into a target scene under a parent node. This is enough to distinguish it from create_scene (makes a new scene) and add_node (adds a non-scene node), though it 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to choose this over create_scene, add_node, or duplicate_node, and no prerequisites (e.g. scene must be open/saved). The usage is only implied by the verb 'Instance'.

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