Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_signals

Retrieve signals defined on a specific node in the running Godot game by providing its node path, so you can inspect event connections and debug gameplay behavior.

Instructions

Get signals defined on a node in the running game.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path in the running game

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 supplied, so the description carries the full disclosure burden. 'Get' implies a read-only lookup, but the definition says nothing about whether the game must be paused/running, what happens if the node path is invalid, or whether the result includes signal names only or their connections.

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?

It is a single front-loaded sentence with no filler or redundancy. Brevity is appropriate, though the terseness contributes to the gaps in guidance rather than resolving them.

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 tool with no annotations, no output schema, and a near-duplicate sibling, the definition should clarify the runtime requirement and the shape of the returned signals. As written, an agent cannot determine what the response contains or how this differs from get_node_signals.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains node_path. The description only restates that the node lives in the running game, adding no format, path-syntax, or node-resolution detail beyond the schema.

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 ('Get') and resource ('signals defined on a node') with a scoping qualifier ('in the running game'), so the operation is understandable in isolation. However, it does not differentiate itself from the near-identical sibling get_node_signals, leaving an agent unable to tell which of the two to pick.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase 'in the running game' hints at a required runtime context but never states that condition as a usage rule, and the overlapping sibling get_node_signals is not addressed.

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