Skip to main content
Glama
Sign In
Godot MCP

Godot MCP

by MhrnMhrn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

godot_run_scene

Execute a specific scene from a Godot project to test gameplay, debug functionality, or verify scene behavior during development.

Instructions

Run a specific Godot scene from an existing 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": {
      "project_path": "<project_path>",
      "scene_path": "<scene_path>"
    },
    "name": "godot_run_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYesPath to the Godot project directory or its project.godot file.
scene_pathYesPath to the target .tscn file. Absolute, relative, and res:// paths are supported.
headlessNoWhether to run the scene in headless mode.
godot_executableNoOptional explicit path to the Godot executable or .app bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Run' implies execution, it doesn't describe what 'running a scene' entails (e.g., launching the Godot editor? Starting a game instance?), whether it requires specific permissions, what happens to existing running instances, or what output/errors to expect. This leaves significant behavioral gaps for a tool that executes code.

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?

The description is a single, focused sentence with zero wasted words. It front-loads the core purpose without unnecessary elaboration, making it immediately scannable and efficient.

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 tool that executes scenes (a potentially complex operation with side effects), the description is inadequate. With no annotations, no output schema, and minimal behavioral context, it fails to address critical aspects like what 'running' entails, success/failure indicators, or how it differs from similar execution tools in the sibling set.

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?

The schema has 100% description coverage, so all parameters are documented in the structured fields. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't explain path resolution precedence, headless mode implications, or executable version compatibility). This meets the baseline for high schema coverage.

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 clearly states the action ('Run') and target resource ('a specific Godot scene from an existing project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'godot_run_project' or 'godot_run_with_capture', which would require more specific scope clarification.

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?

The description provides no guidance on when to use this tool versus alternatives like 'godot_run_project' (which runs the main scene) or 'godot_run_with_capture' (which captures output). There's no mention of prerequisites, typical use cases, or exclusions, leaving the agent to infer usage from tool names alone.

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