Skip to main content
Glama

set_device_parameter

Changes a single device parameter by index and returns the old and new values as displayed in Ableton Live; look up indexes and ranges first with get_device_parameters.

Instructions

Change one device parameter. Look up indexes and ranges with get_device_parameters; the reply shows the old and new values as Live displays them.

Parameters:

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

  • device_index: Position of the device in the chain

  • parameter_index: The parameter's index

  • value: New value, in the parameter's own range

  • 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>",
      "parameter_index": "<parameter_index>",
      "value": "<value>"
    },
    "name": "set_device_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
track_typeNotrack
track_indexYes
device_indexYes
parameter_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.2/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 and it does disclose two useful behaviors: the reply echoes old and new values 'as Live displays them', and value must lie in the parameter's own range. It does not say what happens if the value is out of range, whether the change is undoable or persisted to the project, or whether it requires the device to exist/be enabled - meaningful gaps for a mutation tool.

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?

Front-loaded with the action and the lookup prerequisite, then a compact bulleted parameter list. The bullet list partially mirrors schema field names, but because the schema has zero descriptions that repetition is justified rather than wasteful; only minor trimming is possible.

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?

A five-parameter mutation tool with no annotations needs strong prose, and this covers the units/semantics of every argument plus a note on the reply shape (the output schema exists, so return values needn't be spelled out further). Remaining gap is error/edge behavior - out-of-range values, invalid indexes, persistence - which an agent would want before calling blindly.

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 description coverage is 0%, so the prose must carry all parameter meaning, and it does: track_index is interpreted per track_type (return index for 'return', ignored for 'master'), device_index is the position in the chain, parameter_index identifies the parameter, and value is in the parameter's own range. It also effectively defines the track_type domain ('track' default, 'return', 'master') that the schema leaves as a bare string with no enum.

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?

States a specific verb and resource ('Change one device parameter') and immediately distinguishes itself from the sibling lookup tool by telling the agent to use get_device_parameters for indexes and ranges. The agent can tell this is the write counterpart to the read tool without opening either schema.

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?

Gives a clear, actionable prerequisite: look up indexes and ranges with get_device_parameters before calling, which is the main failure mode for this kind of indexed-write tool. It stops short of explicit exclusions (e.g., when to use set_device_sidechain or other setters instead), but the core routing guidance is present.

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