Skip to main content
Glama

get_node_signals

Read-only

Lists all signals defined on a Godot node along with their current connections, so you can verify signal and method names before connecting or disconnecting signals.

Instructions

List all signals defined on a node and their current connections. Use before connect_signal/disconnect_signal to verify signal/method names. The connections[].target field is already scene-root-relative in the "root/..." form connect_signal/disconnect_signal accept as targetNodePath (a self-connection reports as "root") - pass it straight through with no conversion. Returns: nodeType and signals[], each with name and current connections (signal/target/method). Errors if node not found.

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>",
      "nodePath": "<nodePath>"
    },
    "name": "get_node_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodePathYesNode path from scene root (e.g. "root/Button")
scenePathYesScene file path relative to the project
projectPathYesPath to the Godot project directory

Output Schema

NameRequiredDescriptionDefault
signalsYes
nodePathYes
nodeTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.1
    • addedOutput schema / required
      Added value: +[
      +  "nodePath",
      +  "nodeType",
      +  "signals"
      +]
  2. Changed1 schema field changedv3.6.0
    • addedOutput schema / properties / signals / items / properties / connections / items / properties / target / description
      Added value: +"Scene-root-relative path in \"root/...\" form (a self-connection is \"root\"), directly usable as targetNodePath in connect_signal/disconnect_signal. \"unknown\" for a freed or null object."
  3. Addedv3.1.1
  4. Removedv3.0.0
  5. Addedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true, so the description carries the rest: it discloses the return structure (nodeType, signals[] with name and connections signal/target/method) and the error behavior ('Errors if node not found'). It also proactively documents a non-obvious data contract — that connections[].target is already scene-root-relative and must be passed straight through to targetNodePath, with 'root' for self-connections — which is exactly the kind of trap that causes failed invocations.

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?

Purpose is front-loaded in the first sentence, followed by usage, data-contract, return, and error details in a logical order with no filler. The long parenthetical about root/... paths is dense but earns its length by preventing a real conversion bug.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only three-parameter lookup with an output schema, everything an agent needs is present: what it returns, that it errors on a missing node, and how to reuse the returned target path directly. Nothing material is left to inference.

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 three path parameters are already documented in the schema, and the description adds nothing about their formats or relationships. The path-conversion note concerns the output's target field rather than an input parameter, so it does not raise this dimension above the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List all signals defined on a node and their current connections'), which is clearly distinct from get_node_properties or get_scene_tree. The scope is unambiguous and an agent can select it without opening the schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition — 'Use before connect_signal/disconnect_signal to verify signal/method names' — naming both sibling tools and the ordering that makes this the right call. This is actionable routing guidance rather than implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.