Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_device_parameter

Set a device parameter on a track using its raw Live value, with automatic clamping to the parameter's min/max range.

Instructions

Set a device parameter on a track using a RAW Live value (not normalized). The value is clamped to the parameter's min/max. Use get_track_devices to discover the parameter's index, name, and value range.

Parameters:

  • track_index: which track the device is on

  • device_index: position of the device in the track's device chain (0-based)

  • parameter_index: position of the parameter in the device (0-based; index 0 is usually the on/off toggle)

  • value: raw Live value, e.g. 1000.0 for a filter cutoff in Hz

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
track_indexYes
device_indexYes
parameter_indexYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Without annotations, the description discloses clamping to min/max and raw value usage. It does not cover error handling or side effects, which would enhance transparency.

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 concise with a clear main sentence, a helpful usage hint, and a compact bullet list. No extraneous information.

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 setter mutation, the description covers prerequisites (discovery) and behavior (clamping). It omits return value or error cases, but these are minor given the tool's simplicity.

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?

The schema has 0% description coverage, but the description compensates fully by explaining each parameter's meaning, indexing scheme, and providing an example value. This adds significant 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 states the tool sets a device parameter on a track using a raw Live value, distinguishing it from normalized sets. It specifies the action and resource.

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 recommends using get_track_devices to discover parameter indices and ranges, providing clear context. It does not specify when not to use this tool but gives sufficient guidance.

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