Skip to main content
Glama

signal_disconnect

Disconnect a signal connection between two nodes in a Godot scene by specifying source, signal, target, and method.

Instructions

Disconnect a signal connection in a scene.

Category: Signal

Args: project_path: Path to the Godot project directory scene_path: Path to the scene file (relative to project) source_node_path: Path to the node that emits the signal signal_name: Name of the signal to disconnect target_node_path: Path to the node that receives the signal method_name: Name of the method to disconnect

Returns: Success message or error description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYes
scene_pathYes
source_node_pathYes
signal_nameYes
target_node_pathYes
method_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states it disconnects a signal (destructive) but lacks details on side effects, error handling, or required permissions. Minimal transparency.

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

Conciseness3/5

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

The description is short but includes a redundant 'Category: Signal' line and repeats parameter info already in the schema. Could be more concise, but is not overly verbose.

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?

Given 6 required parameters and no annotations, the description should provide more context about when to use, prerequisites, and error scenarios. It is minimally adequate.

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

Parameters2/5

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

Schema description coverage is 0%, but the description only repeats parameter names without additional meaning, format, or examples. It does not compensate for the lack of schema descriptions.

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 'Disconnect a signal connection in a scene.' with a specific verb and resource, and the tool name 'signal_disconnect' directly contrasts with siblings like 'signal_connect' and 'signal_list_connections'.

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, when not to use, or alternatives. The description only states what the tool does, with no context about prerequisites or comparison to 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