Skip to main content
Glama
Sign In
Ableton Producer MCP

Ableton Producer MCP

by kovtun-oleksii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_device_parameters

Read a track device's parameters—name, value, minimum, and maximum—so you can inspect settings before adjusting or automating them.

Instructions

Read all parameters for a device on a track (name, value, min, max).

Parameters:

  • track_index: Track that owns the device (-1 = master track)

  • device_index: Index into the track's device chain

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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_indexYes
user_promptNo
device_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5+automation.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does disclose that this is a non-mutating read and names the shape of the returned data, but says nothing about failure modes for out-of-range track_index/device_index or latency/refresh behavior.

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?

Purpose is front-loaded in one sentence, followed by a tight parameter list where each line adds distinct meaning. No redundant or padding text.

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 values need not be explained, and all three parameters are documented with real semantics. The remaining gap is behavioral: with no annotations, nothing covers error handling or state requirements for a device-chain index lookup.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate entirely, and it does: track_index is defined as the owning track with the special '-1 = master track' convention, device_index as the position in the track's device chain, and user_prompt as telemetry-only. The master-track sentinel is meaning the bare integer schema could never convey.

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 ('Read all parameters for a device on a track') and even enumerates the returned fields (name, value, min, max). The read semantics implicitly contrast with sibling set_device_parameter, though it never names that sibling explicitly.

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?

No explicit when-to-use or when-not-to-use guidance and no prerequisites (e.g., the device must exist). The read/param-dump purpose makes the typical workflow — inspect parameters before calling set_device_parameter — obvious enough to be only implied.

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