Skip to main content
Glama

Setup TDAbleton Bridge

setup_tdableton

Automatically configures an Ableton Live bridge in a TouchDesigner container, exposing tempo, beat, track, and device parameters as binding-ready Null CHOPs using palette or OSC fallback.

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
hostNoAbleton host IP for the OSC Out CHOP.127.0.0.1
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
nameNoContainer baseCOMP name.tdableton
port_inNoUDP port TD listens on (Live → TD).
port_outNoUDP port TD sends to (TD → Live).
parent_pathNoParent COMP to host the container (default '/project1')./project1
track_countNoNumber of /live/track/<i>/volume channels to materialise as bind-ready Nulls.
include_tempoNoAdd Null CHOPs for tempo, beat, and bar.
expose_devicesNoIf true, generate /live/track/<i>/device/<j>/parameter/<k> listener rows up to device_param_count.
include_masterNoAdd Null CHOPs for /live/master/volume and /live/master/crossfader.
device_param_countNoPer-track device-param count to materialise (used only when expose_devices).
Behavior5/5

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

The description fully discloses the tool's behavior: probing, cloning, or building OSC fabric, with consistent fallback. It aligns with annotations (readOnlyHint=false, destructiveHint=false) and adds context about non-destructive setup.

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 description is four sentences, front-loaded with the key action, and contains no redundant information. Every sentence adds value, making it efficiently informative.

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?

Given the 11 parameters are fully described in the schema and annotations are present, the description adequately explains the tool's purpose, modes, and output. It mentions downstream bind_to_channel, but could briefly note error handling or prerequisites.

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

Parameters3/5

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

Schema coverage is 100%, so the description adds minimal new parameter meaning. It references tempo/beat/track/device channels which relate to parameters, but the schema already provides full descriptions. Baseline score of 3 is appropriate.

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 container, detailing two modes and the output of binding-ready Null CHOPs. It distinguishes itself from siblings like setup_body_tracking by focusing specifically on Ableton integration.

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

Usage Guidelines4/5

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

The description implies usage before bind_to_channel calls and mentions fallback behavior, but lacks explicit guidance on when not to use this tool or direct comparisons with alternatives. The context is clear enough for an experienced user.

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