Skip to main content
Glama

Create audio-reactive visual

create_audio_reactive

Create a real-time audio-reactive visual by building an audio analysis chain (spectrum, level, optional beat) and rendering a spectrum visual in various styles (bars, radial, particles, ring, LED grid).

Instructions

Build an audio analysis chain (spectrum + level + optional beat) and a spectrum visual driven by it. Creates a new baseCOMP under parent_path holding the audio source, an Audio Spectrum CHOP, an Analyze level, an optional Beat CHOP, a CHOP-to-TOP texture with a Sensitivity gain, the GLSL visual, and a Null output. Each visual_style renders the spectrum its own way: glsl=horizontal bars, geometric=radial bars, particle=dot field, feedback=ring tunnel, instancing=LED grid. Returns a summary plus a JSON block with the container path, created node paths, the output path, exposed controls, any node errors, warnings, and an inline preview image. This is the only audio tool that produces a built-in visual: use extract_audio_features for level/bass/mid/treble channels or create_spectrum for per-band channels (no visual), and bind_audio_reactive to wire those channels onto an existing COMP's knobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
duck_depthNoHow deeply the duck pulls toward 0 at peak level (0–1).
parent_pathNoParent network where the audio-reactive container is created (default '/project1')./project1
audio_sourceNoWhere audio comes from: 'microphone'/'device_in' create an Audio Device In CHOP, 'file' an Audio File In CHOP (set audio_file_path), 'existing_chop' reuses an audio CHOP you already have (set existing_chop_path).microphone
visual_styleYesHow the spectrum is rendered: glsl=horizontal bars, geometric=radial bars, particle=dot field, feedback=ring tunnel, instancing=LED grid.
beat_detectionNoWhen true (default), add a Beat CHOP driven by the audio source for tempo/beat signals.
sidechain_duckNoWhen true, add an inverted duck-envelope channel to the modulation Null CHOP (`mod1`).
transient_gateNoWhen true, add a transient/onset channel to a new modulation Null CHOP (`mod1`) for binding to parameters.
audio_file_pathNoPath to an audio file to play; used only when audio_source='file'.
duck_release_msNoRelease time of the duck envelope in ms.
expose_controlsNoWhen true (default), expose a live 'Sensitivity' knob controlling how strongly the audio drives the visual.
frequency_bandsNoSpectrum resolution: sets the Audio Spectrum CHOP output length (TouchDesigner clamps it to 128–4096 bins). Higher = finer spectrum.
transient_hold_msNoTransient hold time in ms before decay; used only when transient_gate=true.
existing_chop_pathNoPath of an existing audio CHOP to analyze; used only when audio_source='existing_chop'.
transient_thresholdNoTransient threshold (0–1); used only when transient_gate=true.
Behavior5/5

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

The description details the exact nodes created (Audio Spectrum CHOP, Analyze level, optional Beat CHOP, etc.), the visual style options, and the return format (summary, JSON block with paths, controls, errors, preview). Annotations (readOnlyHint=false, destructiveHint=false) are consistent, and the description adds significant behavioral context beyond 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 concise, front-loaded with what the tool does, lists visual styles in a compact way, and ends with usage guidelines. Every sentence adds value; no redundancy.

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 14 parameters, no output schema, and the complexity of creating an audio-reactive chain, the description covers the main aspects: what is created, visual styles, return value, and alternatives. It lacks information on prerequisites or failure modes but is otherwise thorough.

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 description coverage is 100%, so baseline is 3. The description adds overall context (e.g., 'sidechain_duck adds an inverted duck-envelope channel') but does not elaborate on individual parameters beyond what the schema already provides. It slightly enhances understanding of the chain structure.

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 an audio analysis chain and a spectrum visual, creating a specific baseCOMP with defined nodes. It distinguishes itself from sibling tools like extract_audio_features, create_spectrum, and bind_audio_reactive, making its purpose unambiguous.

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?

The description explicitly provides when to use this tool versus alternatives, stating it is the only audio tool that produces a built-in visual and listing what other tools are for (e.g., extract_audio_features for channels without visuals). This gives clear usage guidance.

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