Skip to main content
Glama

Create two-way control surface (OSC/MIDI with feedback guard)

create_two_way_surface

Bidirectionally map a hardware controller (OSC/MIDI) to TouchDesigner parameters and echo changes back, using epsilon-delay and rate-limiting to prevent feedback loops.

Instructions

Build a bidirectional OSC or MIDI control surface that drives TouchDesigner params from a controller AND echoes outgoing changes back to it (motor faders, RGB pads), with an oscillation guard so the device's own echo doesn't ping-pong. Each mapping pairs a device address with a TD parameter; a Script CHOP gates outbound sends by epsilon delta, rate limit, and a last_in cache. Exposes Bypass, Globaleps, Ratehz, Reseccache custom pars on the container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContainer name.two_way_surface
parentNoParent COMP path./
protocolNoTransport: 'osc' uses OSC In/Out CHOPs; 'midi' uses MIDI In/Out CHOPs.osc
hostNoOSC remote host (device IP) for outgoing messages. Ignored for MIDI.127.0.0.1
portNoOSC remote port for outgoing messages. Ignored for MIDI.
listenPortNoOSC local port for incoming messages. Ignored for MIDI.
midiDeviceNoMIDI device name (required when protocol='midi').
mappingsYesPer-control routing + guard config.
rateLimitHzNoOutgoing send-rate cap (Hz). Outbound channels are throttled below this rate.
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate mutation but no destruction. The description adds rich behavioral details: Script CHOP gating, epsilon delta, rate limit, last_in cache, and exposed custom pars. No contradiction with annotations.

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 three sentences, front-loaded with purpose, and each sentence adds essential information without redundancy. No wasted words.

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 complexity (9 params, nested array), the description covers the core mechanism, guard features, and custom pars. Lacks mention of error handling or default behavior, but is sufficient for an agent to understand usage.

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 baseline is 3. The description adds value by explaining the mapping concept (device address to TD parameter) and the guard mechanism, but does not go into per-parameter details beyond what the schema already provides.

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 it 'build a bidirectional OSC or MIDI control surface' with specific features like feedback guard. It distinguishes from siblings like 'create_control_surface' by emphasizing bidirectionality and oscillation guard.

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 implies usage when bidirectional control with oscillation guard is needed but does not explicitly state when to use this tool over alternatives like 'create_control_surface' or 'create_midi_map'. No exclusions or when-not-to-use guidance provided.

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