Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

attach_script

Attach scripts to Godot scene nodes, enabling AI assistants to automate game development and scene management.

Instructions

Attach script to node. (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": "attach_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It fails to explain side effects (e.g., whether this overwrites existing scripts), prerequisites (node selection state vs explicit parameters), or what 'Compatibility tool' implies (legacy support, deprecation, etc.).

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?

The description is brief (6 words), but brevity crosses into under-specification. While not verbose, the '(Compatibility tool)' fragment consumes space without adding actionable information, and critical details about the attachment mechanism are omitted.

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?

For a state-mutating tool with no output schema and undocumented parameters, the description is insufficient. It does not address how the target node or script are specified (likely via additionalProperties), error conditions, or whether the operation is idempotent.

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?

Schema description coverage is 0% for both timeoutMs and autoConnect. The description adds zero information about what these parameters control (e.g., connection timeouts to the Godot editor, auto-connecting signals) or what additional properties are accepted via additionalProperties: true.

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

Purpose3/5

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

States the basic action ('Attach script to node') but provides minimal context. Does not clarify what 'attach' entails in the Godot context (e.g., assigning a Script resource to a Node), nor how to specify which node or script. The phrase '(Compatibility tool)' is opaque and unexplained.

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 no guidance on when to use this tool versus siblings like create_script, edit_script, or assign_shader_material. The '(Compatibility tool)' parenthetical hints at limited applicability but fails to explain when it should or should not be preferred over standard workflows.

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