Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

connection_delete

Disconnect an input or output connection on a TouchDesigner operator path. Specify the index to remove that link and return updated connection details.

Instructions

Alias of conn.delete.

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.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds some value by showing that inputIndex and outputIndex 'disconnect this input/output,' and 'Alias of conn.delete' signals canonical behavior. However, it does not mention permanence, side effects, permissions, or failure behavior for what is evidently a destructive operation.

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 parameter documentation is terse, well-ordered, and free of filler; each line earns its place. The high-level purpose is compressed into a single alias clause, so the structure is efficient but the opening is under-explanatory.

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 no annotations and no output schema, a destructive delete tool needs clearer purpose, usage, and side-effect context. The description covers parameter meaning well but leaves the agent guessing about when to call it, how it differs from conn_delete/connection_create, and what a successful deletion returns.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by giving operational meaning to all five parameters: path is the Operator path, inputIndex/outputIndex identify which connection endpoint to disconnect, and detail/response_format enumerate their allowed values and defaults. This is genuinely helpful beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Alias of conn.delete.' but never states in plain terms that this tool deletes a connection. The verb and resource are inferable from the name and the alias, but the object and effect are not explicitly defined, and the description does not clarify how it relates to the sibling conn_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?

There is no guidance on when to use this tool versus alternatives such as conn_create, conn_get, or conn_delete. 'Alias of conn.delete' implies equivalence with another operation but does not name the sibling tool or provide any selection criteria, prerequisites, or exclusions.

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