Skip to main content
Glama
Sign In
Gear

Gear

by wvfp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

editor-launch

Opens the Godot editor GUI for a project, allowing visual inspection and manual editing of scenes and scripts. Requires a project directory with a project.godot file.

Instructions

[compact alias of launch_editor] Opens the Godot editor GUI for a project. Use when visual inspection or manual editing of scenes/scripts is needed. Opens a new window on the host system. Requires: project directory with project.godot file.

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": "editor-launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesAbsolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool 'opens a new window on the host system,' which is a key behavioral trait. However, it does not indicate whether the tool blocks, returns a status, or what happens if the project is already open. More behavioral details would improve transparency.

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 extremely concise: three sentences with no fluff. It front-loads the purpose and alias, then gives usage guidance and requirements. Every sentence earns its place.

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?

Given there is one parameter with 100% schema coverage and no output schema, the description is reasonable but incomplete. It lacks information about blocking behavior, error conditions (e.g., missing project.godot), and return values. For a launch tool, these details are important for an agent to know the consequences of invoking it.

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?

Schema coverage is 100%, so baseline is 3. The description's mention of 'project directory with project.godot file' is redundant with the schema parameter description. The schema already provides clear semantics for the parameter, so the description adds no additional meaning.

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 clearly states the verb ('opens') and resource ('Godot editor GUI for a project'). It also distinguishes from siblings by specifying 'when visual inspection or manual editing is needed,' which contrasts with siblings like editor-run (likely used for running the project). The mention that it is a compact alias of launch_editor adds clarity.

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

Usage Guidelines4/5

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

The description explicitly states when to use ('when visual inspection or manual editing...') and provides a prerequisite ('Requires: project directory with project.godot file'). However, it does not explicitly mention when not to use or name alternative tools, even though the context of siblings implies alternatives.

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