Skip to main content
Glama

get_clip_automation

Read a clip's parameter automation envelope sampled at a chosen beat resolution; returns whether that parameter is automated.

Instructions

Read a clip's envelope for one parameter, sampled every resolution beats; has_envelope=false when that parameter isn't automated in the clip.

Parameters:

  • track_index, clip_index, location: as for set_clip_automation

  • device_index, parameter_index, mixer_parameter: as for set_clip_automation

  • resolution: Sampling step in beats (default 1)

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>"
    },
    "name": "get_clip_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
clip_indexYes
resolutionNo
track_indexYes
device_indexNo
mixer_parameterNo
parameter_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose the sampling semantics and the meaning of has_envelope=false, which is genuine behavioral context. It omits permission/auth requirements, what happens with an invalid device_index or parameter_index, and whether mixer_parameter and parameter_index are mutually exclusive.

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 behavior is front-loaded in one sentence and the parameter notes are compactly itemized with zero filler. The bulleted cross-references are terse to the point of being unhelpful on their own, but nothing is wasted.

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-value documentation is correctly omitted apart from the useful has_envelope flag. For a 7-parameter tool with 0% schema coverage, the reliance on set_clip_automation for parameter meaning leaves real gaps, though the tool's core contract is still legible.

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 0% across 7 parameters, so the description must compensate. It explains 'resolution' well (sampling step in beats, default 1) but defers six parameters to 'as for set_clip_automation', forcing a cross-tool lookup, and never explains the -1 default on device_index or mixer_parameter's role.

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 opening sentence gives a specific verb and resource ('Read a clip's envelope for one parameter') plus the sampling scope, and the name contrasts naturally with set_clip_automation. It stops short of naming the sibling explicitly to sharpen the read-vs-write distinction, but an agent can still tell what this returns.

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 guidance, and no alternative is named — get_device_parameters and get_clip_notes are plausible confusions left unaddressed. The only routing hint is a parameter cross-reference to set_clip_automation, which tells the agent how to fill fields, not when to pick this tool.

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