Skip to main content
Glama

create_scene

Idempotent

Create a new Godot scene file with one root node (Node2D, Node3D, or Control) to start a scene from scratch and save it at a project-relative path.

Instructions

Create a new scene file with a single root node, written to scenePath. Use to start a scene from scratch; to add nodes to an existing scene use add_node. rootNodeType defaults to Node2D: pass "Node3D" for 3D or "Control" for UI. Saves automatically and overwrites an existing file silently. Returns: the scenePath that was written. Errors while a runtime session is live on this project.

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>"
    },
    "name": "create_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenePathYesScene file path relative to the project (e.g. "scenes/main.tscn")
projectPathYesPath to the Godot project directory
rootNodeTypeNoRoot node type (default: Node2D)

Output Schema

NameRequiredDescriptionDefault
warningsNo
scenePathYesProject-relative path of the scene file that was written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.0.1
    • addedOutput schema / properties / scenePath / description
      Added value: +"Project-relative path of the scene file that was written."
    • removedOutput schema / properties / success
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "scenePath"
      +]
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Changed1 schema field changedv2.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "scenePath": {
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Addedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations supply only idempotentHint=true, so the description carries the behavioral burden and does: it discloses auto-save, that an existing file is overwritten silently (a destructive consequence not implied by the annotation), the return value, and the live-session error condition. No contradiction with idempotentHint — re-running with the same arguments produces the same file.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and destination, then usage routing, then the parameter default, then side effects and errors — every sentence carries distinct information with no restatement of the name.

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

Completeness5/5

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

An output schema exists, yet the description still names the return value cheaply; combined with the overwrite warning, default root node type, and live-session error, an agent has everything needed to call this correctly on first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by documenting rootNodeType's default (Node2D) and its useful accepted values ('Node3D' for 3D, 'Control' for UI) even though the schema declares no enum. It adds no semantics for projectPath or scenePath beyond what the schema already says.

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?

States a specific verb and resource ('Create a new scene file') plus the key scope detail that only a single root node is created, and names the sibling it is not (add_node) so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use ('start a scene from scratch') and the alternative when adding to an existing scene ('use add_node'), plus a blocking precondition: it errors while a runtime session is live on the project. That is the when/when-not/alternatives pattern in miniature.

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