Check if the Godot editor is running with the godot_mcp_bridge plugin enabled. Use this to verify the live editor connection before sending scene-editing commands.
Checks whether the Godot editor is running with the godot_mcp_bridge plugin enabled.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does 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. It implies a read-only check but does not specify the return value (e.g., boolean indicating success/failure), error behavior if the editor is not running, or whether the check has any side effects. This is a significant gap for a zero-parameter tool where the agent must know what to expect.
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?
The description is a single, concise sentence that is front-loaded with its core purpose. It contains no fluff or redundancy. Every word contributes to the agent's understanding of what the tool does.
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?
The tool is simple (0 params, no output schema), but the description still lacks critical context. It does not explain what the agent will receive (e.g., a boolean, a message, or an error if the editor is missing). It also does not position the tool among its siblings, such as whether it should be called before other editor tools. This makes it incomplete for an agent that needs to decide when and how to use it.
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?
The tool has no parameters, and the schema reflects that. Per the rule for 0 params, the baseline is 4. The description does not need to explain parameters since there are none, and the schema coverage is effectively 100%. The description adds no parameter-related value because there is nothing to add.
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?
The description states a specific verb ('Checks') and resource ('whether the Godot editor is running with the godot_mcp_bridge plugin enabled'). This clearly distinguishes it from sibling tools like editor_run_scene or editor_get_selection, which perform different operations. The purpose is immediately unambiguous.
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 description provides no guidance on when to use this tool versus the many sibling editor tools. It does not mention that it could be used as a prerequisite check or as a way to verify the environment before invoking other tools. There is no explicit when-to-use or when-not-to-use context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.