Read every parameter of an Ableton Live 12 device by track and device index, returning min, max, quantized status, raw value, and normalized value for precise control.
Reads all parameters of an Ableton Live 12 device (Device.parameters), including min, max, quantized status, raw value, and normalized value.
| Name | Required | Description | Default |
|---|---|---|---|
| track_index | Yes | Zero-based track index. | |
| device_index | Yes | Zero-based device index. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the returned fields (min, max, quantized status, raw value, normalized value), which is genuinely useful, but says nothing about invalid indices, error behavior, or output size for devices with many parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the resource identifier and the payload contents are packed in efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read tool with no output schema, the description adequately covers what is returned and the scope. Only the absence of guidance on locating valid device indices keeps it short of complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both track_index and device_index documented as zero-based indices. The description adds no parameter-level information beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Reads all parameters of an Ableton Live 12 device (Device.parameters)'. This is clearly distinct from mutating siblings like live12_device_set_parameter or live12_device_toggle, though the description does not name those alternatives explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as live12_device_list (to discover devices first) or live12_device_set_parameter (to write). The read-only intent is only implied by the verb 'Reads'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.