Skip to main content
Glama

list_autoloads

Read-only

Lists a Godot project's registered autoloads with paths and singleton flags by reading project.godot directly, helping diagnose headless failures before operations dispatch.

Instructions

List the autoloads registered in a project, with their paths and singleton flags. Use first when diagnosing headless failures: an autoload that stops the engine before an operation is dispatched fails every headless operation. Reads project.godot directly, no Godot process. Returns: autoloads[], each { name, path, singleton }, one per name (the last assignment, which the engine keeps); empty when none. warnings leads when a line is not listed or is not in the form Godot writes.

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": "list_autoloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
warningsNoPresent only when an autoload line could not be parsed, or assigns a name a later line assigns again (neither is listed in autoloads), or when project.godot holds lines that are not in the form Godot writes, named by line number: the engine may register an autoload from such a line that is not listed.
autoloadsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "autoloads": {
      +      "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"
      +    },
      +    "warnings": {
      +      "description": "Present only when an autoload line could not be parsed, or assigns a name a later line assigns again (neither is listed in autoloads), or when project.godot holds lines that are not in the form Godot writes, named by line number: the engine may register an autoload from such a line that is not listed.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "autoloads"
      +  ],
      +  "type": "object"
      +}
  2. Addedv3.1.1
  3. Removedv3.0.0
  4. Addedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool reads project.godot directly with no Godot process, that duplicate names keep the last assignment, that no autoloads yields an empty list, and how warnings are emitted for malformed lines. These are meaningful behavioral details an agent could not infer from the annotations or schema alone.

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 purpose, then usage guidance, execution behavior, return shape, and warning semantics. Each sentence adds distinct information, and there is no redundant restatement of the tool name or annotations.

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 one-parameter read-only diagnostic tool with an output schema, the description supplies everything needed: when to call it, that no engine is launched, the return structure, duplicate-name semantics, empty-result behavior, and warning behavior. No important context is missing.

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%, so the single projectPath parameter is already documented in the input schema. The description implies the path is used to read project.godot but adds no syntax, constraints, or alternative meanings beyond that; baseline 3 is appropriate when the schema carries parameter semantics.

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 first sentence names a specific verb and resource: list the autoloads registered in a project, including paths and singleton flags. It clearly distinguishes this read operation from siblings such as add_autoload and remove_autoload, and the mechanism (reads project.godot directly) further pins down what the tool does.

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?

The description gives a strong usage cue: use it first when diagnosing headless failures, explaining why autoload failures break every headless operation. It does not explicitly name alternatives or when-not-to-use conditions, but the diagnostic context is clear enough for tool selection.

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