Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

attach_script

Attach an existing script to a node in the current scene using the node path and script path.

Instructions

Attach an existing script to a node in the current scene.

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": {
      "node_path": "<node_path>",
      "script_path": "<script_path>"
    },
    "name": "attach_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path to attach the script to
script_pathYesres:// path to the script file

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 supplied, so the description must carry the full behavioral burden, and it does not. For a mutating tool it omits whether an existing attachment is replaced or rejected, whether the scene must be saved afterward, and whether editor/plugin context is required.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though brevity here comes partly from omitting information rather than from tight editing.

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 low-complexity two-parameter tool with a fully documented schema and no output schema, the definition covers the essentials. It remains incomplete for a mutation with zero annotations, since it says nothing about overwrite behavior or the effect on the open scene.

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%, with both node_path and script_path documented, so the schema already does the heavy lifting. The description only adds the framing that the script must already exist and that the node lives in the current scene, which is modest added meaning.

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 a specific verb and resource pair ('Attach an existing script') plus the target ('a node in the current scene'), which is enough for an agent to separate it from detach_script or create_script. It stops short of naming an alternative explicitly, so it is clear rather than distinguishing.

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 or when-not-to-use guidance. The word 'existing' weakly implies create_script is for writing new scripts, but the description never says so, nor does it state preconditions such as the node existing or the script being valid.

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