Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

detach_script

Removes a script from a Godot node by specifying its node path, letting you detach behavior without editing the scene manually.

Instructions

Remove the script attached to a node.

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>"
    },
    "name": "detach_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path to detach the script from

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?

With no annotations supplied, the description carries full behavioral burden but only says 'remove'. It does not say whether the underlying script file is deleted or merely unlinked, whether the change is undoable, what happens if the node has no script, or whether an editor/running-game 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 zero filler, though it is arguably too terse for a mutation operation. Nothing is redundant, but nothing is elaborated either.

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?

Although the tool is simple (one required parameter, no output schema), it is a mutating operation with no annotations, and the description omits failure modes and side effects on the script resource. An agent cannot tell whether calling this destroys the script file or only the attachment.

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% and there is a single required node_path parameter already documented in the schema. The description adds no further meaning such as accepted path formats (relative vs absolute, scene-root syntax), so the baseline of 3 applies.

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?

The description states a specific verb+resource pair ('Remove the script attached to a node') that clearly separates it from attach_script and edit_script. It is unambiguous about what is being operated on (the script attachment on a node), though it does not name the siblings it differs from.

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 guidance on when to use this versus attach_script, edit_script, or create_script; the agent must infer from the tool name alone. No prerequisites are stated, such as whether the node must currently have a script attached.

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