Skip to main content
Glama

Map live data channels onto visual params

create_data_reactive

Map live data channels from a CHOP to numeric custom parameters on any COMP, with range remapping and optional smoothing to avoid visual jitter.

Instructions

Wire arbitrary external data (weather, follower count, sensor readings, OSC values) onto a COMP's custom numeric parameters — the data counterpart to bind_audio_reactive. Point target at a COMP with numeric custom-parameter knobs, source_chop at a live-data CHOP (e.g. a create_data_source Null), and provide explicit mappings (data channel → param name) each with an input range [in_min, in_max] and output range [out_min, out_max] so the data is correctly re-mapped to the parameter's visual range. Set smooth > 0 to insert a Lag CHOP (symmetric attack+release) so noisy or jittery data does not flicker the visuals. Fail-forward: a missing source CHOP or absent channel are warnings — only a missing/non-COMP target is fatal. Build the data CHOP first with create_data_source; use bind_to_channel for finer single-parameter control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smoothNoSymmetric smoothing in seconds (Lag CHOP) applied to all channels so noisy data does not jitter visuals. 0 = no smoothing.
targetYesCOMP whose numeric custom parameters should react to the data.
mappingsYesExplicit data→param mappings with per-mapping range remap. Data is rarely 0–1, so set in_min/in_max to the real data range for correct visual mapping.
source_chopYesCHOP carrying the live data channels (e.g. a create_data_source Null). Channels can be weather values, follower counts, sensor readings, etc.
Behavior5/5

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

The description discloses important behavioral traits beyond annotations: fail-forward error handling (warnings vs fatal), the insertion of a Lag CHOP when smooth > 0, and symmetric attack+release smoothing. Annotations only state readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description adds concrete operational details without contradiction.

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?

Every sentence earns its place, covering purpose, setup, parameter mapping, smoothing, error behavior, and alternatives without redundancy. The structure is logical and front-loaded with the core action, making it efficient and easy to scan.

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 the tool's complexity (4 params, nested mappings, no output schema), the description is remarkably complete: it covers prerequisites, data flow, range remapping, smoothing behavior, error handling, and relationship to sibling tools. No significant gaps remain.

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?

Although schema coverage is 100%, the description adds meaning beyond the schema by explaining the role of each parameter in the workflow: pointing target at a COMP with numeric custom-parameter knobs, source_chop at a live-data CHOP, and explicit mappings with input/output ranges. This goes beyond the field-level schema descriptions.

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's purpose: wiring arbitrary external data onto a COMP's custom numeric parameters. It uses specific verbs ('wire', 'map') and identifies the resource (COMP parameters) and scope (live data channels). It distinguishes itself from siblings by calling itself 'the data counterpart to bind_audio_reactive' and referencing bind_to_channel for finer control.

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 explicit usage guidance: build the data CHOP first with create_data_source, use bind_to_channel for finer single-parameter control, and explains the fail-forward behavior. This clearly states when to use this tool versus alternatives, fulfilling the 'when/when-not/alternatives' criterion.

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/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server