Skip to main content
Glama

write_envelope

DestructiveIdempotent

Replaces or clears automation for one mixer or device parameter in a Session clip using time-ordered points; values ramp between points unless a jump is set.

Instructions

Replace one parameter's automation in a Session clip with these points, or clear it with no points. Values ramp from point to point unless a point has jump=true. Works for the mixer (volume, pan, sends) and device parameters, including rack macros; MIDI CC is not reachable (use CC Control's Custom A, CC 64 Sustain, for the pedal). Copy the clip to the Arrangement to keep the automation there. One undo step.

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": "<track>",
      "slot": "<slot>",
      "parameter": "<parameter>"
    },
    "name": "write_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesClip slot: the scene row, from 0. Example: 0 for the first scene.
trackYesTrack address: t0 for the first track (numbers from 0), rA for return track A, m for the master. Example: t2
pointsNoPoints in time order. Example: [{"time": 0, "value": "200 ms"}, {"time": 8, "value": "800 ms"}]. Empty: clear the envelope.
parameterYesvolume, pan, send A, or a device parameter on the same track as t0/d0:Release (device address, colon, parameter name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true; the description adds real context on top: the operation replaces one parameter's existing automation (or clears it when points is empty) and costs exactly one undo step, so the agent can reason about reversibility and blast radius. It also discloses interpolation behavior (values ramp point-to-point unless jump=true). The remaining gap is error/edge behavior, e.g. unsorted points or an invalid parameter address.

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 core action is front-loaded in the first clause, and every sentence carries information (scope, exclusion, Arrangement caveat, undo cost). It is dense and somewhat run-on with parentheticals, but no sentence is filler.

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?

For a destructive four-parameter write with no output schema, the definition covers scope, exclusions, interpolation, and reversibility well. The one omission is what the call returns or how failures surface, which the description leaves entirely unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already documented with examples and formats, which sets the baseline at 3. The description reinforces which parameter families are addressable and clarifies the ramp/jump semantics, but adds little syntax or format detail beyond what the schema already supplies.

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 first sentence states a specific verb and resource with scope: replace (or clear) one parameter's automation inside a Session clip. That is clearly distinguishable from read_envelope (reading), write_clip (clip content), and edit_notes (MIDI notes) without opening a schema.

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?

It names what is in scope (mixer volume/pan/sends, device parameters including rack macros) and explicitly excludes MIDI CC, pointing to the CC Control Custom A / CC 64 Sustain route for the pedal. It also warns that automation lives in the Session clip and must be copied to the Arrangement to persist there, which is exactly the when-and-when-not guidance an agent needs.

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