Skip to main content
Glama

Create external I/O

create_external_io

Bridge TouchDesigner with external devices via OSC/MIDI input/output, DMX/Art-Net lighting, RTMP streaming, and NDI/Syphon-Spout video input.

Instructions

Bridge TouchDesigner to the outside world: OSC/MIDI input (a control surface — bind incoming channels straight to parameters), OSC/MIDI output (send a CHOP's channels back out for bidirectional feedback to lighting desks, other apps or hardware — pass source_path), DMX/Art-Net output for lighting (dmx_out for any DMX desk; artnet_out for network Art-Net/sACN pixel-mapping of LED strips & stage fixtures), RTMP output to live-stream a TOP to Twitch/YouTube/OBS (rtmp_out — NVIDIA GPU on Windows only), or NDI / Syphon-Spout video input. To discover which channel a control sends (a 'MIDI learn'), wiggle it and read the input CHOP with get_td_nodes, then bind_to that channel. Validate live where possible, but real signal needs the hardware/sender present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhat to bridge: OSC/MIDI/keyboard/gamepad/mouse input (a control surface — bind channels to parameters), OSC/MIDI output (send a CHOP's channels back out for bidirectional feedback — pass source_path), DMX/Art-Net output for lighting (dmx_out is the general DMX desk; artnet_out is a network-only Art-Net/sACN preset for pixel-mapping LED strips & stage fixtures — both send a CHOP's 0-255 channels and need source_path), RTMP output to live-stream a TOP to Twitch/YouTube/OBS-ingest (rtmp_out — pass source_path = the TOP to stream and url; needs an NVIDIA GPU on Windows), or NDI / Syphon-Spout video input. (Window/recording/NDI/Syphon *video outputs* live in setup_output.)
parent_pathNoCOMP to create the I/O operator in./project1
nameNo
portNo(osc_in) UDP port to listen on / (osc_out) port to send to. Defaults to 7000.
normalizeNo(midi_in) How to scale incoming MIDI values.0to1
bind_toNo(osc_in/midi_in) Map incoming channels to parameters. Each binding tolerates a channel that hasn't arrived yet (falls back to 0 instead of erroring).
source_pathNo(dmx_out/artnet_out/osc_out/midi_out) CHOP whose channel values are sent out, or (rtmp_out) the TOP to stream. Should live in the same COMP as parent_path so the wire/source connects.
interfaceNo(dmx_out) DMX transport. (artnet_out forces a network protocol via `net`.)artnet
netNo(artnet_out) Network DMX protocol: Art-Net or sACN (streaming ACN). Defaults to Art-Net.
universeNo(dmx_out/artnet_out) DMX universe.
net_addressNo(dmx_out/artnet_out) Target IP address for Art-Net / sACN.
urlNo(rtmp_out) Full RTMP destination as {service url}/{stream key}, e.g. 'rtmp://live.twitch.tv/app/live_xxx'. If omitted but stream_key is given, prefix with rtmp_base.
rtmp_baseNo(rtmp_out) Ingest base URL to combine with stream_key when url is not given (defaults to YouTube's primary ingest).
stream_keyNo(rtmp_out) Stream key, appended to rtmp_base as '{rtmp_base}/{stream_key}'.
fpsNo(rtmp_out) Frame rate to stream at. Defaults to 30.
activeNo(rtmp_out) Start streaming immediately. Defaults off so the artist can confirm the URL before going live.
source_nameNo(ndi_in/syphon_spout_in) Name of the NDI source or Spout sender to receive.
Behavior5/5

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

Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) are consistent. Description adds context: bindings tolerate missing channels, defaults like port=7000, normalize=0to1, and active defaults off to confirm URL. No contradiction.

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 long but front-loaded with the main purpose. Every sentence adds value, though some details could be condensed. For 17 parameters and complex nuances, it's appropriately detailed.

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 no output schema and 17 parameters, the description covers behavioral aspects, validation hints, and hardware requirements. Lacks explicit mention of return value or state, but completeness is high overall.

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 94%, baseline 3. Description adds value beyond schema: explains MIDI learn process, notes that bind_to tolerates missing channels, clarifies DMX transport defaults, and mentions GPU requirement for RTMP. However, some redundancy exists with 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 bridges TouchDesigner to external I/O including OSC, MIDI, DMX, Art-Net, RTMP, NDI, Syphon/Spout. It enumerates many specific kinds and distinguishes from sibling tool setup_output for video outputs.

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

Usage Guidelines5/5

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

Provides explicit guidance: how to discover channels with MIDI learn, mentions validation requires hardware, and explicitly distinguishes where video outputs live (setup_output). Also notes RTMP requires NVIDIA GPU on Windows.

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