Skip to main content
Glama

find_signal_connections

Locate signal connections for specific nodes in Godot scenes or search for signal usage across entire projects to understand event-driven workflows.

Instructions

Find all signal connections for a node in a scene, or all connections for a signal name across the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneNoPath to the .tscn file
nodeNoNode name to find connections for
signalNoSignal name to search across all scenes

Implementation Reference

  • The handler function that executes the 'find_signal_connections' logic, querying an index for signals or node connections.
    handler: async (ctx) => {
      const { scene, node, signal } = ctx.args;
      if (scene) validatePath(scene);
    
      let results: SignalConnectionResult[] = [];
    
      if (signal) {
        const entries = await index.findSignalByName(signal);
        results = entries.map((e) => ({
          signalName: e.connection.signalName,
          sourceNode: e.connection.sourceNode,
          targetNode: e.connection.targetNode,
          targetMethod: e.connection.targetMethod,
          scenePath: e.scenePath,
        }));
      } else if (scene && node) {
        const sources = await index.getSignalConnections(scene, node);
        const targets = await index.getSignalListeners(scene, node);
        results = [
          ...sources.map((e) => ({
            direction: "emits" as const,
            signalName: e.connection.signalName,
            targetNode: e.connection.targetNode,
            targetMethod: e.connection.targetMethod,
          })),
          ...targets.map((e) => ({
            direction: "receives" as const,
            signalName: e.connection.signalName,
            sourceNode: e.connection.sourceNode,
            targetMethod: e.connection.targetMethod,
          })),
        ];
      }
    
      // Include declarations if searching by signal name
      let declarations: SignalDeclarationResult[] = [];
      if (signal) {
        declarations = (await index.getSignalDeclarations(signal)).map((d) => ({
          name: d.name,
          parameters: d.parameters,
          scriptPath: d.scriptPath,
          line: d.line,
        }));
      }
    
      return makeTextResponse({
        data: { connections: results, declarations },
        totalCount: results.length,
        metadata: { source: "index" },
      });
    },
  • The registration and schema definition for the 'find_signal_connections' tool within 'scene-tools.ts'.
    {
      name: "find_signal_connections",
      description: {
        base: "Find all signal connections for a node in a scene, or all connections for a signal name across the project.",
        slots: {
          planning: "Use this BEFORE editing signals to understand existing connection flow.",
          debugging: "Start here to trace signal-related bugs.",
          editing: "Verify connections after making signal changes.",
        },
      },
      schema: {
        scene: z.string().optional().describe("Path to the .tscn file"),
        node: z.string().optional().describe("Node name to find connections for"),
        signal: z.string().optional().describe("Signal name to search across all scenes"),
      },
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. It mentions the tool's dual search modes but doesn't disclose behavioral traits like whether it's read-only, what permissions are needed, how results are returned (format/pagination), error conditions, or performance characteristics. For a tool with no annotation coverage, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that efficiently communicates the tool's dual functionality. Every word earns its place with zero redundancy, making it easy to parse and understand immediately.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is minimally complete. It explains what the tool does but lacks crucial context about return values, error handling, and behavioral characteristics. Without annotations or output schema, the agent must infer too much about how to interpret results.

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 the schema already documents all three parameters. The description implies the parameters are used in two distinct modes (node-focused vs signal-focused search), which adds some semantic context beyond the schema. However, it doesn't provide format examples, constraints, or interaction rules between parameters.

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?

The description clearly states the tool's purpose with specific verbs ('find all signal connections') and resources ('node in a scene', 'signal name across the project'). It distinguishes itself from sibling tools like 'connect_signal' and 'disconnect_signal' by focusing on discovery rather than modification, and from 'trace_signal_chain' by not implying chain traversal.

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

Usage Guidelines4/5

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

The description provides clear context for usage: either find connections for a specific node in a scene OR search for a signal name across the entire project. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the many sibling tools, which prevents a perfect score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woohq/godette-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server