Skip to main content
Glama

Create envelope follower

create_envelope_follower

Build an attack/release envelope follower with gate or ducking mode to create sidechain pumping effects from any CHOP channel.

Instructions

EXPERIMENTAL — Build a reactive signal-shaping chain (attack/release envelope + threshold gate or sidechain ducking) from a CHOP channel, for 'pump the whole layer on every kick' or similar sidechain effects. Creates a container with: a Select CHOP isolating the source channel by absolute path (no cross-container wire), a Lag CHOP shaping the attack/release envelope, a Logic+Math CHOP threshold gate (gate mode: silence the output below threshold) or an inverted Math CHOP (duck mode: output dips to 0 on a hit, rises on silence — classic sidechain pumping), and a Null CHOP as the stable output handle. Optionally binds the shaped output to target parameters by expression. The gate threshold uses a Logic CHOP whose par names (convert/boundmin/boundmax) match detect_onsets — but these are UNVERIFIED across TD builds; gate reads near 0 at the 0.2 default with most sources — tune threshold live. Use bind_to_channel with attack/release for a simpler Lag-only envelope without a gate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoWhere to build the follower chain (a COMP path, e.g. '/project1')./project1
nameNoBase name for the container COMP that holds the chain.envelope_follower
source_chopYesPath of the CHOP carrying the trigger channel (e.g. '/project1/audio/features' or an onset Null).
channelYesChannel name to follow from source_chop (e.g. 'bass', 'kick', 'level'). The Select CHOP isolates it by name.
attackNoEnvelope rise time in seconds — how quickly the output climbs after a hit (fast = punchy, e.g. 0.001–0.05).
releaseNoEnvelope fall time in seconds — how slowly the output decays after the signal drops (slow = smooth tail, e.g. 0.1–0.8).
thresholdNoGate threshold [0–1]. Below this level the output is silenced (gate) or held at 1 (duck). Start low (0.05–0.2) and raise if false triggers occur. NOTE: gate thresholding uses a Logic CHOP whose par names may vary by TD build — EXPERIMENTAL.
modeNogate: pass the shaped envelope only while it is above threshold — silences the output when the signal is quiet. duck: sidechain/ducking — the output dips toward 0 on every hit and returns to 1 on silence (inverted gate, classic pumping compressor feel).gate
targetsNoOptional list of 'nodePath.parName' targets to bind to the shaped envelope output by expression. Omit to just build the chain (the Null CHOP output can be bound later with bind_to_channel).
Behavior4/5

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

Annotations indicate mutability and non-destructiveness; the description adds specific behavioral details: it creates a container with Select CHOP, Lag CHOP, Logic+Math CHOP, and Null CHOP. It discloses that gate threshold uses unverified par names across TD builds and recommends live tuning. This goes beyond annotations, though annotations already cover the safety profile.

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?

The description is a single paragraph that effectively front-loads the purpose and experimental warning. While it contains substantial detail, every sentence serves a purpose (e.g., explaining internal nodes, alternatives, tuning). It could be slightly more structured, but it balances completeness with readability.

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 9 parameters and no output schema, the description explains the output (Null CHOP) and optional binding. It covers the tool's full functionality, including internal node composition and experimental caveats. It doesn't address error handling or performance, but for a complex creative tool, it is 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%, but the description adds value by explaining how parameters relate to the overall chain (e.g., attack/release shaping, threshold tuning, mode purpose) and provides usage tips (e.g., 'start low 0.05-0.2 and raise'). It enriches the schema descriptions without being redundant.

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 a 'reactive signal-shaping chain (attack/release envelope + threshold gate or sidechain ducking)' from a CHOP channel, with an example 'pump the whole layer on every kick'. It uses specific verbs and resources, and distinguishes from siblings like the simpler 'bind_to_channel' which is mentioned as an alternative.

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 says when to use the tool (for sidechain effects) and provides an alternative: 'Use bind_to_channel with attack/release for a simpler Lag-only envelope without a gate.' It also gives tuning advice and warns about experimental gate parameters, offering clear context on when this tool is appropriate.

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