Disconnect a previously established signal connection in Godot by specifying sender, signal, receiver, and method. Includes undo support.
Disconnect a previously connected signal (undoable).
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| from | Yes | ||
| method | Yes | ||
| signal | Yes |
Changes observed during successful MCP inspections.
v1.12.1v1.10.1v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds 'undoable' which communicates revertibility, a useful behavioral detail. It also states 'previously connected' which sets a precondition. This adds context beyond the readOnlyHint=false and destructiveHint=false annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no extraneous words, earning a high score for structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 4 required parameters and no output schema, this description is too thin. It does not explain parameter roles, what 'undoable' means precisely, or what happens if the signal isn't connected.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema descriptions cover 0% of parameters, and the description offers no parameter semantics. The parameter names (from, to, signal, method) provide weak hints but are undefined, so the agent must infer meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Disconnect' and the resource 'signal', making the tool's action clear. The qualifier 'previously connected' sets scope and distinguishes it as the inverse of connect_signal among siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'previously connected' implies the tool should be used when undoing a signal connection, but it does not explicitly name alternatives or exclusions, leaving the usage guidance implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.