Launch a chosen scene in the Godot editor for immediate testing, replicating the Play Scene action.
Tells the running Godot editor to play a specific scene (like pressing the Play Scene button).
| Name | Required | Description | Default |
|---|---|---|---|
| scene_path | Yes | e.g. "res://scenes/Main.tscn" |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the core behavior (sending a play command to the running editor), but it does not mention side effects, like whether current playback is stopped, whether unsaved changes are affected, or whether the call blocks until the scene loads. The analogy provides some context but not full transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single concise sentence that immediately states the action and includes a useful analogy. No wasted words; all content earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, one-parameter command tool with no output schema, the description plus schema coverage are sufficient for an agent to call it correctly. It lacks details on failure modes or return behavior, but these are less critical given the low complexity and the editor-control nature.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter scene_path is already documented with an example. The description adds no extra meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action and resource: tells the running Godot editor to play a specific scene, with a helpful analogy to pressing the Play Scene button. This clearly distinguishes it from siblings like editor_stop and run_headless, which are about stopping or running without the editor.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The analogy implies usage context (when you want to start a scene in the editor), but there is no explicit guidance on when to use this versus sibling tools like run_headless or editor_stop. No alternatives or exclusions are mentioned, so usage is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.