Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

conn_create

Wire one TouchDesigner operator's output to another operator's input, defining source and destination paths with optional output and input indices.

Instructions

Wire two ops together (output -> input).

fromPath (<class 'str'>): Source operator path.

toPath (<class 'str'>): Destination operator path.

fromOutput (int | None): Source output index (default 0).

toInput (int | None): Destination input index (default 0).

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
detailNo
toPathYes
toInputNo
fromPathYes
fromOutputNo
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

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden and does disclose the connection direction and response controls (detail and response_format). However, it does not state side effects such as whether an existing connection is replaced, how failures are reported, or what the returned object contains.

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

Conciseness5/5

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

The core action is front-loaded in a single short sentence, followed by a compact parameter list. Every line adds a distinct fact about a parameter, with no filler or redundant prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description documents all parameters and response formatting choices, which covers the essential facts an agent needs to call the tool. It still omits the exact return payload shape, error behavior, and any distinction from connection_create, but these are minor gaps for a straightforward creation tool.

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?

All six parameters are individually explained with meaningful roles, defaults, and allowed values despite the input schema having 0% description coverage. The description fully compensates for the bare schema by defining source/destination paths, output/input indices, detail modes, and response_format.

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 first line uses a specific verb ('Wire') and resource ('two ops') with a direction ('output -> input'), so an agent can tell this creates a data-flow connection. It is clear even without relying on the tool name, though it does not explicitly distinguish itself from the similar-sounding sibling connection_create.

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?

The description gives no guidance about when to use conn_create versus alternatives such as conn_get, conn_delete, or connection_create. No preconditions, exclusions, or alternative-tool hints are provided; the appropriate use is only implied by the verb 'Wire'.

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