WazziCode Godot

Overview Schema Source Related Servers Discussions Admin

editor_reload_plugin

Reload the Godot editor plugin to apply code changes or reset its state. The plugin disables and re-enables, then returns a new session ID or a reconnect notice.

Instructions

Reload the Godot editor plugin.

Disables and re-enables the plugin on the next frame. The response shape depends on whether this MCP server was spawned by the plugin or launched externally:

Plugin-managed (default install): returns a pre-flight ack {status: "reload_initiated", transport_will_drop: true, old_session_id, guidance} immediately. The reload kills this server, so the WebSocket transport drops; reconnect and call session_manage(op="list") to find the new session_id.
Externally launched (e.g. python -m godot_ai --transport streamable-http --port 8000 --reload): waits for the new session to register and returns {status: "reloaded", old_session_id, new_session_id}. If the old bridge disappears and no replacement registers within 15 seconds, raises PLUGIN_DISCONNECTED with data.reason == "reload_timeout" and recovery diagnostics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "editor_reload_plugin"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	No	Optional Godot session to target. Empty = active session.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.1.1Aug 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description fully discloses side effects: it kills the server in plugin-managed mode, drops the WebSocket transport, and can raise PLUGIN_DISCONNECTED on timeout. It also explains recovery steps and response shape differences, going well beyond basic expectations.

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 front-loaded with the core purpose, then uses bolded mode sections and bullet-like details to convey complex transport behavior efficiently. Every sentence carries necessary operational information without fluff.

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 tool with dangerous side effects and no annotations, the description covers both execution modes, return payloads, timeout behavior, error code, and recovery diagnostics. It is sufficiently complete given the optional single parameter and existing output schema.

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% for the single optional session_id parameter, so baseline is 3. The description does not add additional parameter context, but the schema already states it targets a Godot session and defaults to active session.

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 'Reload the Godot editor plugin' — a specific verb and resource. It further clarifies the mechanism ('Disables and re-enables the plugin on the next frame'), clearly differentiating it from sibling editor management tools.

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?

Provides detailed context for both launch modes and expected response behavior, including reconnect guidance and timeout diagnostics. However, it does not explicitly name alternatives or state when not to use this tool relative to siblings like editor_manage or session_manage.

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