messier-live

Overview Schema Source Related Servers Discussions Admin

Get Device Parameters

get_device_parameters

Lists a plugin device's parameter names, values, and ranges on a selected deck track, giving you the map needed to plan automation in Ableton Live.

Instructions

Dump a device's parameter list (names, values, ranges) on a deck's track — for exploring a plugin (Serum2, Infiltrator, ...) before automating it.

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": {
      "deck": "<deck>",
      "device_index": "<device_index>"
    },
    "name": "get_device_parameters"
  }
}

Input Schema

Name	Required	Description	Default
`deck`	Yes
`device_index`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'Dump' and 'exploring' imply a non-mutating read operation, but the description does not explicitly state that it has no side effects, what happens with an invalid device_index, or any permission requirements. These are meaningful gaps, though the read-only nature is reasonably inferable.

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 a single, well-structured sentence with no filler. It front-loads the core action and result, then adds a practical purpose. Every part contributes directly to understanding the tool.

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?

The tool is simple, an output schema exists, and the description covers the return content and purpose. However, it lacks guidance on prerequisites: how to identify a deck, how to obtain a valid device_index, and the relationship to list_deck_devices. This prevents the description from being fully self-sufficient for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 two parameters. It only loosely connects 'deck' and 'device' via 'on a deck's track' and 'a device's parameter list'; it does not explain how to specify deck, whether device_index is zero-based, or how to discover valid device indices. The parameter names in the schema do some work, but the description adds minimal semantic value.

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 clearly identifies the action ('Dump'), the resource ('a device's parameter list on a deck's track'), and the specific content returned (names, values, ranges). This distinguishes it from sibling tools like set_device_parameter (which sets rather than gets) and list_deck_devices (which lists devices rather than parameters).

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 description explicitly states the intended use case: 'for exploring a plugin ... before automating it.' This gives clear context for when to invoke the tool, though it does not explicitly name alternatives or exclusions such as 'use list_deck_devices to find the device index first.'

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