Skip to main content
Glama

device_inventory

Lists all devices in the Ableton Live set—track, return, main, racks, and chains—with what each is and what it is for; optionally includes installed VST/VST3/AU plug-ins by vendor.

Instructions

Everything loaded in the set — every device on every track, return track and the main track, racks with their chains — with what each one is and what it is for (native devices from the Live 12 manual, Max for Live devices, known plug-in families such as Arturia emulations), plus, with installed_plugins=true, the VST/VST3/AU plug-ins installed, by vendor.

Parameters:

  • installed_plugins: Also list the installed plug-ins

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": "device_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
installed_pluginsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose substantive behavior: the traversal scope (all tracks, returns, main, rack chains), the nature of the enrichment (native devices from the Live 12 manual, Max for Live devices, known plug-in families), and the exact effect of the boolean flag. It does not warn that enumerating installed plug-ins may be slow or involve scanning the machine's plug-in database, which is the main remaining transparency gap.

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?

One front-loaded sentence establishes the full scope before the conditional flag, with the parameter documented in a short follow-up line. The parenthetical listing device families is dense but earns its place by telling the agent what quality of metadata to expect.

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?

An output schema exists, so return structure need not be explained, yet the description still summarizes what the records contain, which is helpful for planning. For a one-parameter, read-only inventory tool this is close to complete; only performance expectations for the plug-in listing are missing.

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 for the single boolean, and it does: it states that installed_plugins=true additionally lists VST/VST3/AU plug-ins installed, by vendor, which is meaning the schema does not provide. The default-off behavior is left implicit but is inferable from the schema default.

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?

The description clearly states the resource and scope: an inventory of every device loaded in the set, across every track, return track, main track, and rack chains, enriched with descriptive metadata. It is a specific, non-tautological statement of purpose, but it never names or distinguishes itself from siblings such as device_knowledge or get_device_info, which plausibly overlap in describing what a device is.

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?

Usage is only implied: an agent can infer this is the tool to call when it needs a full picture of the devices present in the session. There is no explicit when-to-use statement, no exclusion against the knowledge/info siblings, and no prerequisites, though the conditional 'with installed_plugins=true' clause usefully signals the opt-in path.

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