Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

launch_editor

Starts the Godot editor for a given project path so AI assistants can begin editing that project.

Instructions

Launch Godot editor for a specific 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": {
      "projectPath": "<projectPath>"
    },
    "name": "launch_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesGodot project path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.4/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, but it only restates the action without explaining side effects, blocking behavior, failure modes, or whether the editor launches in the background. This is a notable gap for a tool that spawns an external process.

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 filler words. It is appropriately concise for such a simple tool, though it could have added a few behavioral details without becoming bloated.

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?

The tool has low complexity with one required parameter fully covered by the schema, so the description is minimally adequate for invocation. However, it lacks information about the execution model, return behavior, and prerequisites, leaving the agent to guess about what happens after launch.

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 description coverage is 100%, and the single parameter 'projectPath' is already described as 'Godot project path'. The description's phrase 'for a specific project' adds minimal meaning beyond the schema, 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.

Purpose5/5

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

States a specific verb ('launch'), a clear resource ('Godot editor'), and a targeting condition ('for a specific project'). Clearly distinguishable from siblings like run_project and create_project, which serve different intents.

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?

The description implies use when the user wants to open the Godot editor for a specific project, but it does not explicitly state when not to use it or mention alternatives. No exclusionary guidance is provided.

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