Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

conn_delete

Disconnect a specified input or output from a node to remove unwanted links and rewire the network.

Instructions

Disconnect an input and/or output of a node.

path (<class 'str'>): Operator path.

inputIndex (int | None): Disconnect this input.

outputIndex (int | None): Disconnect this output.

detail (str | None): full (default) | summary (long lists cut to 25 + count) | minimal (top-level scalars only).

response_format (str | None): yaml (default, token-cheap) | json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
detailNo
inputIndexNo
outputIndexNo
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Detail"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Response Format"
+}
  2. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

There are no annotations, and the description does not disclose side effects, reversibility, failure behavior, or whether existing connections are affected beyond the specified input/output. For a mutation tool, this is a significant transparency gap.

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

Conciseness4/5

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

The description is compact and front-loaded with a clear first sentence, followed by a minimal parameter list. It avoids unnecessary prose, though the parameter documentation could be slightly tightened.

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?

For a five-parameter mutation tool with no output schema and no annotations, important context is missing: return behavior, prerequisites, error conditions, and relationship to connection_delete. The parameter list helps, but the overall tool context is incomplete.

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?

The schema has 0% description coverage, but the description documents every parameter with its purpose and explains the options for detail and response_format. It does not fully specify indexing semantics or whether inputIndex/outputIndex are mutually exclusive, but it provides usable meaning beyond the raw schema.

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 states a specific action, 'Disconnect an input and/or output of a node,' naming both the verb and the resource. It partially distinguishes itself from siblings by focusing on per-port disconnection, but it does not explicitly explain how it differs from the similarly named connection_delete.

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 is given on when to use this tool versus alternatives such as conn_create, conn_get, or connection_delete. The description explains what it does but not in which situations it should be preferred, leaving the agent to guess among close sibling tools.

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

Deploy Server

Other Tools