Skip to main content
Glama

get_clip_notes

Retrieve all MIDI notes in a Session or Arrangement clip with pitch, timing, duration, velocity, and mute data so you can inspect or analyze a clip's note content.

Instructions

All the MIDI notes of a clip: pitch, start_time, duration, velocity, mute (plus probability and velocity deviation when Live has them). Times are in beats from the clip start. For an Arrangement clip the reply also has arrangement_start / arrangement_end and start_marker: without looping, a note sounds at arrangement_start + (start_time − start_marker).

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

  • location: "session" (default) or "arrangement"

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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well: it discloses the return shape, that times are in beats from clip start, that arrangement clips additionally include arrangement_start / arrangement_end / start_marker, and gives the exact timing formula. Gaps remain around failure behavior for non-MIDI clips and any ordering guarantee for the notes.

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 return fields and the Arrangement timing caveat are front-loaded, and the parameter list is compact and scannable. The formula sentence is dense but earns its place, since it conveys semantics not available anywhere else.

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?

With an output schema present, the description needn't enumerate return values, yet it does so usefully (beats units, optional fields). All three params are covered despite 0% schema coverage. What's missing is edge-case behavior on non-MIDI or empty clips, but nothing required to call it correctly is absent.

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?

Schema description coverage is 0%, so the description must compensate and largely does: clip_index is explained as 'Session slot, or position in get_arrangement_clips', and location's allowed values and default are spelled out (the schema has no enum, only a bare string default). track_index is only described as 'The track', which is thin, keeping this below a 5.

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 opens with a specific verb+resource: 'All the MIDI notes of a clip', and enumerates the returned fields (pitch, start_time, duration, velocity, mute, plus probability and velocity deviation). That is clearly distinct from siblings such as get_arrangement_clips (clip listing) or get_clip_automation, so an agent can pick it 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 Guidelines3/5

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

The parameter notes imply the usage context (Session vs Arrangement clip, clip_index referencing get_arrangement_clips), which is helpful routing. But there is no explicit when-to-use/when-not-to-use statement and no named alternative such as get_clip_automation or analyze_clip_music for note analysis.

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