Skip to main content
Glama

read_device

Read-onlyIdempotent

Retrieve Ableton Live device parameters as displayed, including raw values, ranges, and on/off state; inspect rack macros/chains or query specific parameters by name and target.

Instructions

A device's parameters as Live shows them ("262 ms", "-6.0 dB", "On"), with raw value and range, plus whether the device is on.

For a rack: its visible mapped macro knobs and its chains, not every parameter (set all_params to see them all). For other devices: all parameters. Give params to see only some, by name; a wrong name comes back with similar names. A chain or pad address shows its devices instead.

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": {
      "target": "<target>"
    },
    "name": "read_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoOnly these parameters, by name as Live shows them. Example: ["Release", "Decay"]. Leave empty for the default view.
targetYesDevice, rack chain or Drum Rack pad address. Examples: t0/d0 (first device on t0), t1/d0/c1/d0 (first device in chain 1 of that rack), t2/d0/pC1 (Drum Rack pad C1), rA/d0, m/d0
all_paramsNoFor a rack: list every parameter, not only the macros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety needs no restating. The description still adds real behavior: racks return only mapped macros and chains by default, an unknown parameter name yields suggestions ('similar names'), and a chain or pad address resolves to its devices rather than an error. It says nothing about response size limits or ordering, which keeps it from a 5.

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?

Front-loads the return shape in the first sentence, then addresses target-type variants and filtering. The parenthetical example values ('262 ms', '-6.0 dB') help ground the format, though the paragraph is a bit dense in places and could be tightened.

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?

With no output schema, the description carries the return-value burden and does so: it explains the human-readable value format alongside raw value and range, the on/off flag, macro/chain-only default for racks, and chain/pad address indirection. An agent has enough to call it and interpret the result without guessing.

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%, so the schema already explains target addressing syntax, the params name list, and all_params. The description largely echoes that framing and adds only the wrong-name fallback hint. Baseline 3 is appropriate given 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?

States a concrete verb and resource plus the exact content returned ('parameter values as Live shows them', raw value, range, on/off state). It also distinguishes behavior by target type (racks show macros + chains, other devices show all parameters), which sharpens the scope. It stops short of naming a sibling read/modify tool to contrast with, so the boundary with set_device_params or configure_device is only implied.

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?

Offers conditional guidance inside the tool ('give params to see only some', 'set all_params to see them all' for racks), which is useful. However it never says when to prefer this over related tools (e.g., bulk set inspection) or what prerequisites apply. Usage is implied by the read-only nature rather than stated against alternatives.

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