Skip to main content
Glama

Create modulators

create_modulators
Destructive

Build a bank of tempo-synced LFO modulators with adjustable shape, rate, and phase, all outputting on a single Null for direct binding.

Instructions

Build a bank of N BPM-synced LFOs in one self-contained container — each an oscillator (sine/triangle/saw/square or a random sample-&-hold) with its own rate-in-beats, output range and phase offset. Every rate locks to a tempo source (a create_tempo_sync Null, or TouchDesigner's global tempo) by expression, so the whole bank speeds up/slows down with the music and stays phase-continuous across tempo changes. All outputs land on one Null CHOP (mod_out) with one named channel per modulator, ready for bind_to_channel — the 'everything breathes' lever. Note: modulators are timeline-driven, so they only move while the timeline is playing. Re-running with an existing container name rebuilds it in place (clearing that container's children), so this tool is marked destructive and hidden from the safe profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the self-contained modulator-bank container.modulators
parent_pathNoParent COMP the 'modulators' container is created inside./project1
modulatorsYesThe modulators (LFOs) to build. Each becomes one named output channel on the bank's Null.
tempo_sourceNoPath to an existing tempo Null/Beat CHOP carrying a 'bpm' channel (e.g. the Null from create_tempo_sync, '/project1/tempo_sync/tempo'). Omit to create a fresh Beat CHOP locked to TouchDesigner's global tempo inside the bank.
bpm_channelNoName of the BPM channel on the tempo source to lock rates to.bpm
expose_controlsNoExpose a live custom-parameter page on the bank: a master Rate multiplier and a master Depth (amplitude) scale, so you can speed up or flatten the whole bank from one knob during a show.
Behavior5/5

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

The description goes beyond annotations by detailing that modulators are timeline-driven, re-running with same name rebuilds in place (clearing children), and that rates lock to tempo source via expression. This adds significant behavioral context not present in 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 well-structured, front-loading the main purpose then covering details. Every sentence adds value, with no redundancy. It is appropriately sized for the tool's complexity.

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?

The description covers output format (Null CHOP with named channels), dependencies (tempo source, timeline playing), destructive behavior, and usage notes. For a tool with no output schema, this provides complete context for use.

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%, so baseline is 3. The description adds context beyond the schema, such as output landing on one Null CHOP and the overall workflow. It explains the purpose of phase and shape values like 'random' and 'saw', enhancing understanding without repeating schema details.

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 creates a bank of BPM-synced LFOs in a container, specifying verb (build), resource (bank of LFOs), and scope (self-contained, tempo-synced). It distinguishes from siblings like create_tempo_sync by stating its dependency and unique output structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context like timeline dependency and destructive behavior, and mentions output is ready for bind_to_channel. However, it does not explicitly state when to use this tool over alternatives, though the purpose is clear enough to imply usage.

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