Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_autoload

Register autoload singletons in Godot projects, enabling global script access across scenes for persistent state and shared functionality.

Instructions

Register autoload singleton. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. 'Register' implies a write operation to project settings, but description fails to disclose persistence behavior, required editor state, or side effects. The 'compatibility' label is the only behavioral hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (5 words), but underspecified rather than efficiently distilled. The parenthetical is compressed but not informative enough to earn its place given the information gaps elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a project-modifying tool. Lacks explanation of what constitutes a valid autoload, expected lifecycle, interaction with the 'autoConnect' parameter, and return behavior (no output schema exists to compensate).

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

Parameters1/5

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

Complete failure to compensate for 0% schema description coverage. Description mentions neither 'timeoutMs' nor 'autoConnect', leaving critical parameters undocumented. No explanation of what timeout applies to or what auto-connect establishes.

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?

States the specific action (Register) and target resource (autoload singleton). Distinguishes from siblings 'get_autoload' and 'remove_autoload' by verb choice, though assumes familiarity with Godot's autoload concept.

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?

Provides only the cryptic parenthetical '(Compatibility tool)' which hints at legacy usage but offers no explicit when-to-use guidance, prerequisites, or comparison to alternatives like manual singleton instantiation.

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