Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

play_scene

Launch the Godot project or a chosen scene in the game window by passing an optional res:// path.

Instructions

Run the project (or a specific scene) in the Godot game window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "play_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional res:// path to a specific scene to run

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, yet it says nothing about whether the call blocks while the game runs, how the run is terminated (stop_scene exists as a sibling), or what happens if a scene is already running. For a process-launching tool this is a meaningful omission.

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 wasted wording. The parenthetical is slightly awkward but efficient overall.

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?

With no annotations and no output schema, the description is the only behavioral source, and it omits run lifecycle details (blocking behavior, how to stop, state requirements) that an agent needs before invoking a launcher. Adequate for identifying the action, insufficient for calling it safely.

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

Parameters2/5

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

The description only restates the schema: the parenthetical '(or a specific scene)' mirrors the path parameter already documented at 100% coverage. It adds no detail about accepted path formats, defaults, or what happens when path is omitted beyond what the schema states.

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 ('Run') and resource ('the project or a specific scene') in a named target environment ('Godot game window'), which clearly separates it from scene-editing siblings like open_scene. It does not explicitly name or contrast with any sibling, so it stops short of full differentiation.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for launching/playing rather than editing. There is no guidance on when to prefer this over open_scene or how it relates to stop_scene, and no prerequisites such as the project needing to be saved first.

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