Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

connect_signal

Links a signal from a source node to a method on a target node, enabling automated event wiring in Godot scenes.

Instructions

Connect a signal from one node to a method on another 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": {
      "source_path": "<source_path>",
      "signal_name": "<signal_name>",
      "target_path": "<target_path>",
      "method_name": "<method_name>"
    },
    "name": "connect_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
method_nameYesMethod to call on the target node
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 and does not meet it. It does not say whether the connection is persisted to the scene file, what happens if the connection already exists (error vs. duplicate vs. no-op), or whether it requires editor context. For a mutation tool, these are significant omissions.

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, and the directionality of the connection is stated first. It is efficient, though its brevity is partly a consequence of under-specification rather than tight writing.

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?

With no annotations, no output schema, and a mutation action, the description should explain persistence, failure modes, and preconditions. It covers only the conceptual shape of the operation, leaving the agent without enough to call it confidently in edge cases.

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%, so each parameter is already documented, and the baseline is 3. The description does add a small amount of semantic framing by mapping source_path to the emitting node and target_path to the receiving node, but it offers no format details (path syntax, how to reference built-in signals).

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 gives a specific verb and resource ('Connect a signal') and clarifies the two-endpoint model (from one node to a method on another node), which an agent can act on directly. It stops short of differentiating itself from siblings like connect_game_signal or disconnect_signal, so it is clear but not disambiguating.

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 guidance, no prerequisites (e.g., node must exist, editor vs. runtime), and no mention of the inverse operation disconnect_signal. The only implied context is that both nodes already exist, which the agent must infer.

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