Skip to main content
Glama

remove_autoload

Destructive

Unregister an autoload by name from project.godot to recover when a broken autoload blocks headless Godot operations; returns the removed name and remaining autoloads.

Instructions

Unregister an autoload from a project by name. Use to recover from an autoload that stops the engine before headless operations are dispatched. No Godot process is used. Returns: removed (the name) and autoloads[], the entries that remain, read back from project.godot. Errors if no autoload has that 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": {
      "projectPath": "<projectPath>",
      "autoloadName": "<autoloadName>"
    },
    "name": "remove_autoload"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory
autoloadNameYesName of the autoload to remove

Output Schema

NameRequiredDescriptionDefault
removedYesName of the autoload that was removed.
autoloadsYesThe entries that remain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "autoloads": {
      +      "description": "The entries that remain.",
      +      "items": {
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "path": {
      +            "description": "res:// path of the script or scene.",
      +            "type": "string"
      +          },
      +          "singleton": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "path",
      +          "singleton"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "removed": {
      +      "description": "Name of the autoload that was removed.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "removed",
      +    "autoloads"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that no Godot process is used, that the result is read back from project.godot, and that it errors when the name is missing. These are exactly the side-effect and failure-mode details an agent needs before invoking a destructive tool.

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?

Four short sentences, front-loaded with the action and the recovery use case, with no filler. The 'Returns:' sentence partially duplicates the output schema, which is the only minor redundancy.

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 two-parameter destructive tool, the definition covers action, use case, execution model, error behavior, and result shape. With an output schema present, it need not explain return values further, and nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds meaning by establishing that autoloadName must match an existing autoload or the call errors, and that projectPath is a Godot project directory the entries are read back from.

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 a specific verb and resource, 'Unregister an autoload from a project by name', which an agent can immediately distinguish from add_autoload and update_autoload. The 'by name' qualifier and the error condition further pin down exactly what operation is performed.

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?

It gives a concrete triggering scenario: recovering from an autoload that stops the engine before headless operations are dispatched. That is clear when-to-use guidance, but it never names an alternative or states when not to use it, so it stops short of full routing guidance.

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