Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

open_scene

Opens a .tscn scene in the Godot editor from a res:// path, enabling direct inspection or editing of that scene.

Instructions

Open a scene in the Godot editor.

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": {
      "path": "<path>"
    },
    "name": "open_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path to the .tscn file

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 provided, so the description carries the full disclosure burden, yet it says nothing about side effects such as replacing the active editor scene, what happens if a scene is already open, or how invalid paths fail. 'Open' implies editor state mutation, but none of that behavior is described.

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 short sentence with no wasted words and the key action front-loaded. It is efficiently structured, though the brevity comes at the cost of substance rather than being a flaw of verbosity.

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

Completeness3/5

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

For a one-parameter tool with a fully documented schema and no output schema, the definition is minimally sufficient. However, an editor state-mutating tool with no annotations should at least say whether it swaps the current scene and what constitutes failure.

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?

There is only one parameter and schema coverage is 100%, with the schema already documenting 'res:// path to the .tscn file'. The description adds no additional meaning (no path format rules, no relative-path behavior), so the 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 concrete verb and resource ('Open a scene') plus the environment ('Godot editor'), which separates it from create_scene or close_scene. It does not explicitly distinguish opening from get_current_scene or play_scene, so the differentiation is only partial.

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 when-to-use guidance is offered: nothing says whether this replaces the currently open scene, whether a scene must be closed first, or when an agent should prefer create_scene or play_scene instead. The agent must infer the workflow entirely from the 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