Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

analyze_signal_flow

Maps all signal connections for a Godot node and its children, helping you trace event flow and identify linked callbacks before debugging or editing scenes.

Instructions

Analyze and map all signal connections for a node and its children.

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": "analyze_signal_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesRoot node path to analyze

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 burden. It does disclose one behavioral trait—recursive traversal into children—but says nothing about whether the operation is read-only, how deep or costly the traversal is, or what form the resulting signal map takes.

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 redundancy. It is efficient, though its brevity leaves gaps that a second short clause could have closed.

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 one-parameter tool with no output schema, the description covers the core action and scope. However, with zero annotations and no return-value documentation, an agent cannot tell if this is a safe read or what the output looks like, which leaves the definition only minimally adequate.

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% with a single parameter already documented as 'Root node path to analyze'. The description's 'node and its children' phrasing hints at the traversal scope of that path but adds no format or resolution details beyond the schema, so baseline 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 ('analyze and map') and resource ('signal connections') with an explicit scope of 'a node and its children'. It is clear enough to distinguish from mutating siblings like connect_signal or disconnect_signal, though it never names them.

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. With siblings such as connect_signal, disconnect_signal, and analyze_code_complexity present, the description gives no signal about whether this is purely an inspection tool or when an agent should prefer it over those alternatives.

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