Skip to main content
Glama

get_device_parameters

Retrieve every parameter of an Ableton device—index, value, range, and displayed units—for a specified track and device index to inspect or modify settings.

Instructions

Every parameter of a device with its index, value, range and the value as Live displays it (dB, Hz, %, mode names).

Parameters:

  • track_index: The track (return index for "return", ignored for "master")

  • device_index: Position of the device in the chain

  • track_type: "track" (default), "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_parameters"
  }
}

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

A3.6/5.0
Behavior3/5

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

With no annotations, the description has to carry behavioral disclosure, and it does some of that: it defines the return content and notes the quirk that track_index is ignored for 'master' and means the return index for 'return'. It does not state read-only safety, index base (0- vs 1-based), or what happens when the device index is out of range.

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?

The purpose sentence is front-loaded and the three parameter notes are a tight bulleted block with no filler. Slight awkwardness in the opening fragment, but nothing is wasted.

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?

For a three-parameter read tool with two required indices and an output schema already present, the definition covers the parameter contract and the shape of the result well enough to call it correctly. Only index-base and failure behavior are unaddressed, which is minor given the output schema exists.

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 supply all parameter meaning, and it describes all three: track_index, device_index as position in the chain, and track_type with its default 'track', its 'return'/'master' alternatives, and the effect on track_index. The remaining gap is the numbering convention for the two integer indices.

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 and resource: it returns every parameter of a device along with index, value, range, and the Live-displayed value (dB, Hz, %, mode names). That is concrete enough to distinguish it from a generic 'device info' read, though it never names a sibling such as get_device_info or set_device_parameter to sharpen the boundary.

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 read path for device parameters, and the mention of live-displayed values hints at when it is preferable. There is no explicit when-to-use versus get_device_info, and no when-not guidance or statement of prerequisites.

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