Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

reload_plugin

Refresh a Godot editor plugin by name so code or configuration changes take effect without restarting the editor.

Instructions

Reload an editor plugin by name.

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": {
      "plugin_name": "<plugin_name>"
    },
    "name": "reload_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
plugin_nameYesName of the plugin to reload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about side effects. It does not say whether in-memory plugin state is discarded, whether the plugin must already be loaded, what happens if the name is unknown, or whether the call is expensive or blocking. 'Reload' implies re-initialization with possible state loss, and that is never stated.

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?

One short sentence with the action front-loaded and no filler. It is appropriately sized, though the space saved is used for nothing else that would help an agent.

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?

For a one-parameter tool with a fully described schema and no output schema, the definition covers the minimum needed to make the call. It falls short on preconditions and post-call effects, which matter for a reload operation that can disrupt a running editor session.

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?

The single parameter is fully documented in the schema ('Name of the plugin to reload'), and the description's 'by name' adds no format, casing, or naming-convention detail beyond that. With 100% schema coverage, the baseline of 3 is the correct ceiling here.

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

Purpose4/5

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

The description gives a specific verb and resource ('Reload an editor plugin') plus the qualifier 'by name', so the agent knows exactly what operation it performs. It does not distinguish itself from any sibling, but no other plugin-management tool appears in the supplied sibling list, so there is little ambiguity to resolve.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether to call this after editing a plugin's files, only for plugins already enabled, or what alternative to pick if the plugin is not loaded. The agent must infer all of the triggering conditions.

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