Skip to main content
Glama

Make a component react to audio

bind_audio_reactive

Wire any COMP's numeric custom parameters to audio features (level, bass, mid, treble) from a CHOP. Auto-map knobs by name or define explicit param-to-channel bindings with per-binding scale and offset.

Instructions

Make a whole COMP react to the music in one call — the core VJ move. Point target at a COMP with numeric custom-parameter knobs and source_chop at an audio-feature CHOP (e.g. an extract_audio_features Null carrying level/bass/mid/treble), and each knob is switched to expression mode tracking an audio band. Omit mappings to auto-map knobs by name heuristic (bright/level/opacity→level, scale/size/zoom→bass, hue/color→treble, speed/rate/rot→mid; unrecognized knobs are skipped), or pass explicit param→channel bindings with per-binding scale/offset. By default appends a master 'Reactivity' float knob (0–2, default = intensity) that scales every binding so the artist can dial the whole network's reactivity from one control. Fail-forward: a missing source CHOP, an absent channel, or an already-bound parameter are warnings, not failures — only a missing/non-COMP target is fatal. This tool only WIRES an existing COMP to an existing CHOP, building no nodes: produce the feature CHOP with extract_audio_features (or create_spectrum) first, use create_audio_reactive when you want a whole new reactive network with its own visual, and bind_to_channel for finer single-parameter control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesCOMP whose numeric custom parameters (knobs) should react to the music.
mappingsNoExplicit param→channel bindings. Omit to auto-map the target COMP's numeric custom parameters by name heuristics.
intensityNoMaster reactivity amount (0=off, 1=normal, 2=strong) — scales every binding.
add_masterNoAppend a 'Reactivity' master float knob (0-2, default = intensity) on the target COMP that scales every binding.
source_chopYesCHOP carrying audio feature channels (e.g. an extract_audio_features Null). Expected channels: level, bass, mid, treble.
Behavior5/5

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

Disclosures beyond annotations: auto-mapping heuristics, master knob appending, fail-forward warnings, and fatal conditions. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise yet dense, no filler. Front-loaded with core action, then alternatives, then details. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 params, no output schema, and annotations present, description covers usage, behavior, error handling, and sibling contrasts completely.

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

Parameters5/5

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

Schema coverage 100%; description adds auto-mapping heuristic details (bright→level, scale/size→bass, etc.) and clarifies intensity scale. Highly informative.

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?

States 'Make a whole COMP react to the music in one call' with specific verb and resource. Explicitly distinguishes from siblings create_audio_reactive and bind_to_channel.

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 clear when-to-use vs alternatives, lists prerequisites (produce feature CHOP first), and describes fail-forward behavior. Complete 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