Skip to main content
Glama

read_envelope

Read-onlyIdempotent

Retrieve automation points for a Session clip parameter, including beat times, displayed and raw values, and curve bends; returns exists=false when no envelope is defined.

Instructions

The automation points of one parameter in a Session clip: time in beats, value as Live shows it, raw value, and curve bends. exists=false when the clip has no envelope for it.

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": "read_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
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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. Beyond that, the description discloses the return payload shape (time in beats, display value, raw value, curve bends) and a meaningful edge case: exists=false when the clip has no envelope for that parameter. That absence flag is exactly the kind of behavioral detail annotations cannot convey.

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?

Two sentences, dense and front-loaded, with the payload contents stated before the exists=false caveat. No filler wording. Minor deduction for opening with a bare noun phrase rather than a verb-led statement of action, which slightly delays the 'this reads' framing.

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?

There is no output schema, so the description correctly spends its words enumerating the returned fields and the empty-case signal. Combined with a fully documented three-parameter schema and clear read-only annotations, an agent has enough to call this correctly. The main residual gap is guidance on alternatives such as write_envelope for modification.

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 description coverage is 100%, with each of track, slot, and parameter already documented including examples and address syntax. The description adds only the framing that the parameter is scoped to a Session clip and that a single parameter is targeted. This meets the baseline of 3, where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource and scope: automation points for one parameter inside a Session clip, with the returned fields (time in beats, displayed value, raw value, curve bends) enumerated. It is a noun phrase rather than a verb, but an agent can still tell this is the read side of envelope access and distinguish it from write_envelope and read_clip. It does not explicitly name the sibling it is not.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use statement, and no alternative is named (e.g. use read_clip for note/loop data, write_envelope to modify). The only contextual hint is the phrase 'in a Session clip', which implies usage but does not guide selection. An agent must infer the calling conditions from the sibling name alone.

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