Skip to main content
Glama

get_device_info

Retrieve a specific Ableton Live device's real name, kind, latency, and API details such as sidechain routing, plug-in presets, Simpler state, and rack chains/variations.

Instructions

One device's identity (Live's real device name even when a preset renamed it, kind, latency) and its specific API: sidechain routing and options (Compressor), plug-in presets, Simpler sample/slicing state, rack chains and variations.

Parameters:

  • track_index / device_index: The device

  • track_type: "track", "return" or "master"

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

Input Schema

NameRequiredDescriptionDefault
track_typeNotrack
track_indexYes
device_indexYes

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?

No annotations exist, so the description carries the burden. It does disclose useful behavioral content beyond a bare label: what identity fields come back and that the real device name is returned even when a preset renamed it, and that output varies by device kind. It does not state that the call is read-only or what happens for an invalid index.

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-loaded with the payload summary, then a short parameter block. No filler sentences, though the two index parameters get a single shared gloss that is thinner than the rest of the prose.

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

Completeness3/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 values needn't be explained, and the description covers the device-specific dimensions. However, with 0% schema description coverage on three parameters and no annotations, the definition leaves read-only behavior and index semantics under-specified for a lookup tool.

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 coverage is 0% and the schema gives only types, so the description must compensate. It supplies the valid track_type values (track/return/master), which the schema lacks, but reduces track_index/device_index to 'The device' without saying they are indices into a track's chain or that they are zero-based.

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 specific verb+resource: retrieves one device's identity (real Live device name even when a preset renamed it, kind, latency) plus its device-specific API surface (sidechain, plug-in presets, Simpler state, rack chains/variations). That is concrete enough to distinguish it from a parameter-listing tool, though it never names the alternatives.

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 explicit when-to-use, when-not-to-use, or alternative routing. An agent can infer this is an inspection call for a single device, but nothing tells it why to pick this over get_device_parameters or device_inventory for the same device.

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