Skip to main content
Glama

create_scene

Create a new Godot .tscn scene with one root node by specifying the project, scene path, root name, and root type.

Instructions

Create a new .tscn scene with a single root 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": {
      "project": "<project>",
      "scene_path": "<scene_path>",
      "root_name": "<root_name>",
      "root_type": "<root_type>"
    },
    "name": "create_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject folder name under the projects directory
root_nameYesRoot node name (identifier)
root_typeYesRoot node Godot class, e.g. "Node2D", "Control", "CharacterBody2D"
scene_pathYesScene path relative to the project, e.g. "scenes/level1.tscn"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 behavioral burden. It implies a write operation but does not disclose overwrite behavior when scene_path already exists, whether intermediate directories are created, whether an existing project is required, or what the tool returns. Only the 'single root node' constraint adds context.

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 or redundancy. It is efficient, though the brevity is also the source of the missing behavioral detail.

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

Completeness4/5

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

For a four-parameter creation tool whose parameters are fully documented in the schema and which has no output schema to explain, the description covers what is made and where. It is only marginally incomplete regarding overwrite/error behavior, which matters for a mutation tool without annotations.

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 four parameters are already documented in the schema with examples (Godot classes, relative scene path). The description's phrase 'single root node' corroborates root_name/root_type but adds no new meaning such as path format constraints or naming rules.

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 (Create) and resource (.tscn scene) plus the scope constraint that only a single root node is produced, which separates it from add_node and create_script. It does not explicitly contrast with siblings such as create_project, 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?

There is no when-to-use guidance, no prerequisites (e.g., that the project must already exist), and no exclusions or alternative tools named. An agent must infer entirely from the tool name that this is the scene-creation step of a project setup flow.

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