Skip to main content
Glama

Create automation lane

create_automation_lane

Records a live parameter sweep into a circular buffer, then loops playback on a bar-phase clock for automatic parameter modulation.

Instructions

Build a per-parameter automation lane that records a live parameter sweep into a circular buffer over N bars, then loops the recording back into the parameter on a bar-phase clock. Two modes: record (sample the target param every cook into a ring buffer) or loop (read the buffer back via Lookup CHOP bound to the target param). Re-calling with the same name and a different mode flips the state without rebuilding the network. Uses Beat CHOP → Select CHOP (rampbar) → Lookup CHOP playback, with COMP storage tracking mode/write_head/armed state. Returns a summary plus a JSON block with container path, mode, samples count, target, and any warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSystem container name, e.g. 'auto_lane_filter'
parentNoParent COMP path, defaults to '/'
targetParamYesOP path + param tuple, e.g. '/project1/filter1:cutoff'
barsNo
bpmNo
modeNorecord
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false) and no destruction (destructiveHint=false). The description adds rich behavioral details: internal component chain (Beat CHOP → Select CHOP → Lookup CHOP), state tracking via COMP storage, and the re-call flip mechanism. No contradictions with annotations.

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 reasonably concise, spanning multiple sentences but without fluff. It is front-loaded with the main purpose, then details modes, re-call behavior, internal components, and return value. Could be slightly more structured but effectively communicates all necessary information.

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 the tool's complexity (6 parameters, no output schema), the description covers purpose, modes, re-call behavior, internal architecture, and return format. It lacks error conditions or prerequisites but is otherwise complete for an experienced user.

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?

With 50% schema description coverage, the description compensates by explaining key parameters: name as container name, targetParam as OP+param tuple, bars as number of bars for the buffer, bpm as tempo, and modes as record/loop. The optional parent parameter is briefly mentioned in schema but not in description, which is acceptable.

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 per-parameter automation lane for recording and looping parameter sweeps. It specifies the resource (automation lane) and action (build), distinguishing it from sibling tools like 'animate_parameter' or 'bind_to_channel' by focusing on the circular buffer and bar-phase clock mechanism.

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 explains two modes (record/loop) and the ability to flip states by re-calling with the same name and different mode without rebuilding. This provides clear contextual guidance for using the tool effectively, though it does not explicitly contrast with alternatives.

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