Skip to main content
Glama

Create Synesthesia / Unreal OSC preset send

create_synesthesia_unreal_osc

Build an OSC-out preset map to send controls from TouchDesigner to Synesthesia or Unreal Engine. Choose a preset to automatically configure address prefix, port, and control names for the target app.

Instructions

Build a named OSC-out preset map for driving Synesthesia or Unreal Engine from TouchDesigner. Picks a preset ('synesthesia' → prefix '/syn', port 6448; 'unreal' → prefix '/unreal', port 8000), builds a Constant CHOP with one named channel per control (channel name = '/' so an oscoutCHOP emits the exact address the target app expects), and wires it into an oscoutCHOP aimed at host:port. Override the control names, prefix, host, or port as needed. This is the preset layer on top of create_external_io osc_out — it fills in the address templates and default control set so the send 'just works' with the target app. Bind audio/analysis to the source channels (e.g. op('controls')['syn/Bass']) to make the receiving app react.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoDestination IP the OSC messages are sent to (the machine running Synesthesia / Unreal).127.0.0.1
nameNoBase name for the container COMP.osc_send
portNoUDP port to send OSC to. Null uses the preset's default (Synesthesia 6448, Unreal 8000).
activeNoStart sending immediately. Defaults off so you can confirm the destination host/port first.
prefixNoOverride the preset's OSC address prefix (the part before the control name). Null uses the preset default (syn / unreal).
presetNoNamed OSC-out preset — sets the address prefix, default port, and default control names for Synesthesia or Unreal Engine.synesthesia
controlsNoOverride the preset's control names. Each becomes an OSC address '/<prefix>/<name>' and a channel on the source Constant CHOP you drive/bind.
parent_pathNoCOMP to create the OSC-out chain in (default '/project1')./project1
Behavior5/5

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

Description details the creation process (Constant CHOP, oscoutCHOP), default port/prefix behavior, and that 'active' defaults off. This adds significant context beyond annotations (readOnlyHint=false, destructiveHint=false), with no contradictions.

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?

Description is relatively long but each sentence adds value; it front-loads the main purpose and explains the mechanism efficiently. Could be slightly more concise but overall well-structured.

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 8 parameters and no output schema, the description covers the creation process, dependencies (on create_external_io), and intended outcome (OSC-out chain). It also hints at post-creation binding, making it sufficiently 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%, setting baseline at 3. Description adds meaning by explaining how 'preset' sets defaults for 'prefix', 'port', 'controls', and how overrides work, enriching parameter relationships beyond schema alone.

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 builds a named OSC-out preset map for Synesthesia or Unreal Engine, with specific verbs like 'picks', 'builds', 'wires'. It distinguishes from sibling 'create_external_io' by noting it is a preset layer on top, solidifying its unique function.

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?

Provides clear context for when to use (driving Synesthesia or Unreal) and mentions it's a preset layer on top of create_external_io, implying alternative for custom setups. However, it does not explicitly list when-not-to-use or all alternatives.

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