Skip to main content
Glama

launch_editor

Opens the Godot editor GUI for a project so a human can work in it; use only when the user asks to open the editor, not for agent-driven scene or node changes.

Instructions

Open the Godot editor GUI for a project, for the human user. Use only when the user asks to open the editor; for agent-driven work use the headless scene and node tools (add_node, set_node_properties, etc.), since the editor cannot be controlled programmatically. Returns: projectPath, the editor process pid and message. Errors if projectPath has no project.godot or the editor process does not start.

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": {
      "projectPath": "<projectPath>"
    },
    "name": "launch_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
pidYesProcess id of the editor.
messageYes
projectPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "pid": {
      +      "description": "Process id of the editor.",
      +      "type": "number"
      +    },
      +    "projectPath": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "projectPath",
      +    "pid",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that the launched editor is not programmatically controllable, names the return payload (projectPath, pid, message), and specifies two failure conditions (missing project.godot, process failing to start).

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?

Three short sentences, front-loaded with the purpose and the routing rule, followed by returns and errors. No filler or repetition of the schema.

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

Completeness5/5

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

For a one-parameter launch tool, everything an agent needs is present: purpose, the human-only boundary, the alternative tooling, return shape, and error cases.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is self-describing, so the baseline is already met; the description adds real meaning by stating that projectPath must contain a project.godot or the call errors.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Open the Godot editor GUI for a project") and immediately scopes it to the human user, which distinguishes it cleanly from the headless scene/node siblings such as add_node and set_node_properties.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use rule ("Use only when the user asks to open the editor") plus a when-not rule with named alternatives ("for agent-driven work use the headless scene and node tools (add_node, set_node_properties, etc.)") and the reason (the editor cannot be controlled programmatically).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.