Skip to main content
Glama

Extract audio features

extract_audio_features

Extract overall level and bass, mid, treble band energies from an audio source, outputting raw signals on a Null CHOP to drive any parameter in TouchDesigner.

Instructions

Build an audio-analysis chain that exposes ready-to-bind reactive channels — overall level plus bass/mid/treble band energies — on a Null CHOP. Unlike create_audio_reactive (which renders a spectrum visual), this produces the raw signals so you can drive ANY parameter: bind a node parameter to op('…/audio_features/features')['bass'] and it pulses with the music. A Sensitivity knob scales all channels. Source can be the live device (mic/line — may prompt for macOS permission), an audio file, a synthetic oscillator (for testing), or an existing CHOP. Use create_spectrum for N fine per-band channels instead of these four coarse bands, and pass this Null as the source_chop to bind_audio_reactive to make a whole COMP react.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mid_hzNoBand-pass centre for the mid band.
sourceNoAudio source. 'device' = live microphone/line in (the real-world default; creating it may pop a one-time macOS microphone-permission dialog — click Allow). 'file' = an audio file. 'oscillator' = a synthetic tone, handy for testing without any device permission. 'existing_chop' = reuse a CHOP you already have.device
bass_hzNoLow-pass cutoff for the bass band.
treble_hzNoHigh-pass cutoff for the treble band.
parent_pathNoParent COMP path the self-contained 'audio_features' container is created inside./project1
audio_file_pathNoAudio file path (source='file').
expose_controlsNoExpose a live 'Sensitivity' knob (a gain over every feature channel).
existing_chop_pathNoPath of an existing audio CHOP to analyze (source='existing_chop').
Behavior5/5

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

Annotations indicate non-read-only, open-world, non-destructive. Description adds that source='device' may prompt macOS permission, creates a self-contained container, and exposes a Sensitivity knob. 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?

Single paragraph efficiently conveys purpose, differentiation, usage, and behavioral notes without redundancy.

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?

No output schema but description explains return value (reactive channels on Null CHOP) and lists bands. References sibling tools and provides enough context for correct invocation.

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 covers 100% of parameters with descriptions. Description adds context for source values (e.g., macOS permission) and explains the purpose of the tool beyond parameter definitions.

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 builds an audio-analysis chain exposing reactive channels on a Null CHOP. It distinguishes itself from siblings like create_audio_reactive (renders spectrum visual) and create_spectrum (fine per-band channels).

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?

Explicitly contrasts with create_audio_reactive and create_spectrum, advises passing the Null to bind_audio_reactive, and explains when to use each source type (device, file, oscillator, existing_chop).

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