Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

disconnect_signal

Remove a previously connected signal between two Godot nodes by providing the source path, signal name, target path, and method name. Use to clean up or modify signal connections.

Instructions

Disconnect a previously connected signal.

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": {
      "source_path": "<source_path>",
      "signal_name": "<signal_name>",
      "target_path": "<target_path>",
      "method_name": "<method_name>"
    },
    "name": "disconnect_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
method_nameYesConnected method name
signal_nameYesName of the signal
source_pathYesPath of the node emitting the signal
target_pathYesPath of the node receiving the signal

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 provided, so the description carries the full behavioral burden. It says nothing about required permissions, whether the operation is reversible, whether it fails or no-ops when no matching connection exists, or whether other connections are affected, which are key questions for a mutation tool.

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 wasted wording. It is appropriately terse, though that terseness comes at the cost of the behavioral detail noted 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?

For a four-parameter mutation tool with no annotations and no output schema, the definition is too thin. An agent would need to infer error behavior, idempotency, and the relationship to the connect_signal siblings without any support.

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 coverage is 100%, so all four parameters are already documented in the input schema. The description adds no additional meaning about how source_path, target_path, signal_name, and method_name combine to identify the connection, 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 and resource ('Disconnect a previously connected signal'), making the operation immediately clear and distinguishable from connection-creation siblings such as connect_signal. It does not explicitly name those siblings, so it stops short of a 5.

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?

The phrase 'previously connected' weakly implies a connection must already exist, but there is no explicit guidance on when to use this instead of connect_signal/connect_game_signal, no prerequisites, and no note about failure when the connection is absent.

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