Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_scene

Creates a new Godot scene file at a specified project path with a chosen root node type, enabling AI-driven setup of scenes for game development.

Instructions

Create a new scene file in the 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": {
      "name": "<name>"
    },
    "name": "create_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesScene name
pathNores:// path where the scene will be saved
root_typeNoType of the root node (e.g. Node2D, Node3D)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutating tool. It says nothing about overwrite behavior if the target path already exists, whether the new scene is opened in the editor afterward, whether required permissions or an open project apply, or what the call returns on failure.

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?

It is a single front-loaded sentence with no filler or repetition. The brevity is the main weakness only in that nothing substantive follows the core statement.

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 file-creating mutation with zero annotations and no output schema, the description should disclose collision/overwrite behavior and post-creation state, and it does none of that. The 100% schema coverage covers parameter meaning, but the operational behavior an agent needs before calling it is missing.

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 (name, path, root_type) are already documented with their meaning and the example node types. The description adds no additional semantics such as defaults, path conventions, or what root_type falls back to when omitted, so the baseline of 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?

The description uses a specific verb and resource ("Create a new scene file") and scopes it to "the project", which is enough for an agent to distinguish it from sibling operations like open_scene and save_scene. It does not explicitly name any sibling or state how it differs from add_scene_instance, so it falls short of the top score.

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 or when-not-to-use guidance, and no mention of the other scene tools (open_scene, save_scene, add_scene_instance) that could plausibly be confused with it. The agent must infer the selection context entirely from the tool name.

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