Skip to main content
Glama

read_clip_notes

Read-onlyIdempotent

Read MIDI notes from a Session clip, filter them by beat range, or get a quick count for large clips without transferring every note.

Instructions

Read MIDI notes of a Session clip, query a specific window, or count notes.

Returns:
    Dictionary containing notes, count, window parameters, and validation report.

Note:
    Times and positions are expressed in clip-local beats. Muted notes are included
    and carry ``mute: true``. ``time_span`` is a length in beats, not an end beat:
    beats 24 to 32 is ``from_time=24, time_span=8``.

    Windowing and counting keep a small question small. A single drum clip of 384
    notes comes back as 57k characters, past the tool-result cap, so a survey across
    59 clips cannot be a full read of each. The LOM has no ``note_count`` on ``Clip``
    at all, so a count taken out here means transferring every note to measure it.
    ``count_only=True`` counts inside Live and carries back one integer.

    With ``count_only`` there is nothing to validate, so ``check`` is ignored. With a
    window, ``check`` sees the window and not the clip.

    Returned notes are sorted by time, then pitch. Live hands its notes back ordered
    by pitch, which is the one order a musical instruction never means: "the third
    note", "every other note" and "the last note" are all about when a note sounds.
    Four notes written at beats 0, 1, 2, 3 with pitches 72, 60, 67, 62 come back 60,
    62, 67, 72, so taking every other entry off the raw list picks alternating pitches
    rather than alternating beats, silently and plausibly. For Live's own order call
    ``get_notes_extended`` through ``lom_call``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYesClip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down.
checkNoTrue runs validation over the notes that came back and reports what it found. Ignored when count_only is true, since there are no notes to check.
trackYesTrack index in song.tracks, counted from 0.
from_timeNoFirst beat of the window to read, clip-local, where 0 is the clip start. Omit to read from the beginning.
time_spanNoLength of the window in beats, not the beat it ends on: beats 24 to 32 is from_time=24, time_span=8. Omit to read to the end.
count_onlyNoTrue counts the notes inside Live and returns the number without transferring them, which is the way to ask about a large clip.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / check / description
      Added value: +"True runs validation over the notes that came back and reports what it found. Ignored when count_only is true, since there are no notes to check."
    • addedInput schema / properties / count_only / description
      Added value: +"True counts the notes inside Live and returns the number without transferring them, which is the way to ask about a large clip."
    • addedInput schema / properties / from_time / description
      Added value: +"First beat of the window to read, clip-local, where 0 is the clip start. Omit to read from the beginning."
    • addedInput schema / properties / slot / description
      Added value: +"Clip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down."
    • addedInput schema / properties / time_span / description
      Added value: +"Length of the window in beats, not the beat it ends on: beats 24 to 32 is from_time=24, time_span=8. Omit to read to the end."
    • addedInput schema / properties / track / description
      Added value: +"Track index in song.tracks, counted from 0."
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The annotations already indicate a safe read-only operation, and the description adds substantial behavioral detail: muted notes are included with mute:true, time_span is a length not an endpoint, results are sorted by time then pitch, returned data can exceed the tool-result cap, and count_only executes inside Live. This goes far beyond what the annotations or schema convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but tightly organized with Returns and Note sections, and every paragraph carries load-bearing information about behavior, performance, ordering, or parameter semantics. The core purpose is stated up front, and the detailed caveats are front-loaded where they matter most.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with six parameters, an output schema, and subtle ordering and windowing behavior, the description is complete. It covers return values, validation behavior, performance constraints, note ordering, and the right way to count notes in large clips, so an agent can select and invoke it correctly without additional probing.

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?

Even though schema coverage is 100%, the description adds critical semantic nuance: time_span is defined as a duration, count_only transfers only an integer, check is ignored with count_only, and windowed reads validate only the window. The slot and track parameters are already clear from the schema, so the description layers extra meaning where needed.

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 and resource, 'Read MIDI notes of a Session clip', and further distinguishes three modes: full read, windowed query, and note counting. This clearly separates it from write_clip_notes and other siblings while establishing the exact scope of the tool.

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?

The description gives explicit guidance on when to use count_only for large clips, explains how windowing changes the check behavior, and directs users to get_notes_extended through lom_call when Live's native note order is required. This is strong routing advice with concrete alternatives.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server