Skip to main content
Glama

Setup TDAbleton Bridge

setup_tdableton

Create an Ableton Live bridge in a TouchDesigner container. It auto-probes for the TDAbleton Palette or falls back to OSC, then exposes tempo, beat, track, and device channels as bind-ready Null CHOPs.

Instructions

Wire up an Ableton Live bridge inside a tdmcp-managed container. Auto mode probes for the official TDAbleton Palette COMP; if found, clones it and surfaces tempo/beat/track/device channels as binding-ready Null CHOPs. Falls back to a full OSC fabric (oscinCHOP + selectCHOP fan-out) if the Palette isn't available. Either branch exposes the same Null CHOP names at the container boundary so downstream bind_to_channel calls work regardless of which path was taken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent COMP to host the container (default '/project1')./project1
nameNoContainer baseCOMP name.tdableton
modeNoBridge mode. 'auto' = probe palette then fall back to OSC. 'palette' = require Palette (warn on miss, still builds OSC fallback). 'osc' = skip palette probe entirely.auto
hostNoAbleton host IP for the OSC Out CHOP.127.0.0.1
port_inNoUDP port TD listens on (Live → TD).
port_outNoUDP port TD sends to (TD → Live).
track_countNoNumber of /live/track/<i>/volume channels to materialise as bind-ready Nulls.
expose_devicesNoIf true, generate /live/track/<i>/device/<j>/parameter/<k> listener rows up to device_param_count.
device_param_countNoPer-track device-param count to materialise (used only when expose_devices).
include_masterNoAdd Null CHOPs for /live/master/volume and /live/master/crossfader.
include_tempoNoAdd Null CHOPs for tempo, beat, and bar.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the two execution paths, the Null CHOP exposure, and that both branches produce the same interface. However, it omits details like what happens if the container exists or if the palette is missing beyond fallback.

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?

Three sentences, concise, informative, and front-loaded. Every sentence earns its place without unnecessary elaboration.

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

Completeness3/5

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

Given the complexity (11 parameters, no output schema), the description covers high-level behavior but lacks details on exact Null CHOP names and what the tool returns as output. It is adequate but not fully complete.

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?

Schema coverage is 100%, so baseline is 3. The description adds context about the Null CHOPs and binding-readiness, which helps understand parameters like track_count and expose_devices. It adds value beyond the schema descriptions.

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

Purpose5/5

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

The description clearly states the tool wires up an Ableton Live bridge inside a tdmcp-managed container, with specific details about auto and fallback modes. It is a specific verb+resource combination that distinguishes from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the two modes (auto, palette, osc) but does not explicitly state when to use this tool over siblings or when not to use it. It lacks alternative recommendations or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server