Skip to main content
Glama

read_set

Read-onlyIdempotent

Inspect an open Ableton Live Set to see tempo, time signature, loop settings, tracks, return tracks, scenes, locators, and clip assignments at a glance.

Instructions

Overview of the open Live Set: tempo, time signature, loop, tracks, return tracks, scenes and locators.

Each scene lists the clips in its row as {track address: clip name}; empty slots are left out. Each track shows its address, name, kind (midi, audio, group) and device names. Use read_track for one track's mixer, devices and clips.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_set"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: scenes are keyed by {track address: clip name} with empty slots omitted, and each track reports address, name, kind (midi, audio, group) and device names — this tells the agent what shape the response takes and that missing clips simply won't appear.

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?

It is front-loaded with the scope of the read, then details the two structured sections (scenes, tracks), then closes with the sibling pointer. Every sentence carries information; nothing is redundant with the annotations or the empty schema.

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 no output schema, the description has to carry the return shape itself, and it does for scenes and tracks. Locators, loop and time-signature return formats are named but not described, a minor gap for an overview tool whose annotations already settle safety.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies the whole set is read with no filtering arguments.

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 opening sentence gives a specific verb (read/overview) and resource (the open Live Set) and enumerates exactly what is covered: tempo, time signature, loop, tracks, return tracks, scenes and locators. That enumeration distinguishes it from siblings like read_track or read_clip without needing the schema.

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

Usage Guidelines4/5

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

The final sentence explicitly routes the agent to read_track when it needs a single track's mixer, devices and clips, which is a clear use-the-other-tool signal. It stops short of stating exclusions for this tool (e.g. that it does not return clip contents or device parameters), so it is strong but not a full when/when-not map.

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