Retrieves existing output buttons and connections for a specified node ID, so you can inspect a node's available outgoing links before adding or rewiring automation blocks.
Find existing output buttons/connections from a node
| Name | Required | Description | Default |
|---|---|---|---|
| node_id | Yes | The node ID to find buttons for |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description must carry the behavioral burden. It simply states what is found, but fails to describe the behavior (e.g., whether it returns IDs, configurations, or a list of objects) or any limitations.
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 definition is a single, focused sentence. It is highly concise and effectively conveys the tool's main function in one breath.
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?
Given the lack of annotations and output schema, the description is incomplete. It does not define what is returned, making it difficult for an agent to confirm if the tool meets its needs without further trial and error.
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?
With 100% schema description coverage, the parameter semantics are already fully defined in the input schema. The description adds no information that goes beyond the structured fields.
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 clearly identifies the resource (nodes) and the action (finding existing output buttons/connections). While clear, it does not explicitly distinguish this function from the many existing node-related siblings provided in the context.
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 description is a functional statement rather than guidance. It provides no context on when this tool should be used versus alternatives like `node_get_scheme_edges` or `node_get`, leaving the AI to infer the best time to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.