Skip to main content
Glama

signal_list_node_signals

Retrieve all signals from a specific node in a Godot scene to inspect their parameters.

Instructions

List all signals available on a node.

Category: Signal

Args: project_path: Path to the Godot project directory scene_path: Path to the scene file (relative to project) node_path: Path to the node (e.g., "root" or "root/Button")

Returns: JSON containing the node's available signals with their parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYes
scene_pathYes
node_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Description states the tool lists signals and returns JSON, implying a read-only operation. However, without annotations, it does not explicitly confirm no side effects or disclose any behavioral traits like permissions or error conditions.

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?

Extremely concise and well-structured with clear sections (purpose, args, returns). Every sentence is necessary and front-loaded with the main purpose.

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

Completeness4/5

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

Given the tool's simplicity (a list operation) and the presence of an output schema, the description provides sufficient context. It explains the return format and parameter usage, making it complete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaningful explanations for each parameter (e.g., 'Path to the Godot project directory'). This compensates well for the missing schema descriptions.

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 clearly states 'List all signals available on a node' with a specific verb and resource. It is distinct from sibling tools like signal_connect or signal_disconnect, but lacks explicit differentiation.

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?

No guidance on when to use this tool versus alternatives. The description provides parameter names but no context about prerequisites, conditions, or exclusion of other signal tools.

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/ChanceFlow/godot-mcp'

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