Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

connect_signal

Enable event-driven communication in Godot by connecting node signals. Sets timeout and auto-connection parameters for automated game development workflows and scene scripting.

Instructions

Connect node signal. (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": "connect_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/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 full burden. The parenthetical '(Compatibility tool)' hints at behavioral constraints but remains unexplained. The description does not disclose side effects, persistence of connections, or the meaning of the timeout/autoConnect behavior evident in the schema.

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?

Extremely brief (6 words) with no filler or redundancy. However, the second sentence '(Compatibility tool)' does not earn its place as it provides no actionable information without elaboration.

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?

Given the complexity of Godot signal systems (requiring source node, signal name, target node, and method) and the presence of timeout/autoConnect parameters suggesting non-standard behavior, the description is inadequate. No output schema exists, and the description does not explain return values or error conditions.

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%, leaving 'timeoutMs' and 'autoConnect' completely undocumented. The description fails to compensate by explaining these parameters, their valid ranges, or their semantic purpose in signal connection context.

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 ('Connect') and domain object ('node signal'), which in the context of Godot (evident from siblings) has specific meaning. However, it fails to specify connection targets, signal types, or distinguish from sibling tools like 'disconnect_signal' or 'find_signal_connections'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 alternatives such as 'disconnect_signal', 'get_signals', or 'find_signal_connections'. No prerequisites, warnings, or selection criteria are mentioned.

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