Skip to main content
Glama

write_clip_evolution

Write evolving automation envelopes into Session clips and optionally extend MIDI loops over many bars, shaping volume, pan, sends, or device parameters with musical curves.

Instructions

Make a Session clip evolve over many bars: optionally extend it to bars (a MIDI loop is tiled, e.g. 4 -> 64 bars), then write one automation envelope per lane with a musical curve. Copied to the Arrangement (e.g. by build_arrangement), the envelopes become the track's automation there.

Each lane: {"mixer_parameter": "volume" | "panning" | "send:N"} or {"device_index": d, "parameter_index": p}, plus "start", "end" (in the parameter's units, see get_device_parameters: min/max/display), "shape" (linear, exp, log, s_curve, swell, sine, triangle, steps, random_walk, hold), optional "cycles" (sine/triangle), "steps" (steps), "power" (exp/log curvature, default 2.5), "from_bar"/"to_bar" to limit the curve to part of the clip (the value holds outside), "seed".

Example, a 64-bar techno build: filter cutoff exp from 0.3 to 0.9, reverb send swell, hats volume in 8 steps.

Parameters:

  • track_index / clip_index: Session clip

  • lanes: Curves to write (see above)

  • bars: Extend the clip to this many bars first (MIDI clips; 4/4)

  • resolution: Envelope step in beats (1 = a point per beat)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "lanes": "<lanes>"
    },
    "name": "write_clip_evolution"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsNo
lanesYes
clip_indexYes
resolutionNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior: loop tiling on extension, values holding outside from_bar/to_bar, the default power of 2.5, per-lane step resolution, and arrangement-copy semantics. It omits whether existing automation on a lane is overwritten and any permission or failure conditions, which matters for a mutation tool.

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?

Front-loads the operation, then the lane grammar, a worked example, and a parameter recap — each section earns its place for a tool of this complexity. It runs long, but the density is justified by the untyped schema.

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?

An output schema exists, so return values need not be explained. The main residual gap is mutation semantics — whether envelopes replace or merge with existing automation and what happens when bars conflicts with an existing loop length.

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?

Schema coverage is 0% and the lane objects are untyped (additionalProperties: true), so the description must define them entirely — and it does, enumerating mixer_parameter vs device_index/parameter_index addressing, start/end in parameter units, the full shape list, cycles/steps/power/from_bar/to_bar/seed, plus bars and resolution. Without this text the lanes parameter would be uncallable.

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?

States a specific compound action: extend a Session clip to `bars` (with MIDI tiling described concretely as 4 -> 64 bars) and write one automation envelope per lane. The resource (Session clip automation) and effect (envelopes follow the clip into Arrangement) are unmistakable, setting it apart from point-level setters in the sibling list.

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

Usage Guidelines3/5

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

Implies the use case ('a 64-bar techno build') and links to get_device_parameters for parameter units, and notes the payoff via build_arrangement. However it never states when to prefer this over set_clip_automation or get_clip_automation, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools