messier-live

Overview Schema Source Related Servers Discussions Admin

Set Fx Macro

set_fx_macro

Set a named performance FX macro on a selected Ableton Live deck to any intensity from 0.0 to 1.0, enabling precise real-time control during a DJ set.

Instructions

Set a PERF-rack macro on a deck by name (e.g. 'Glitch', 'Space', 'Crush'). value 0.0–1.0.

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": {
      "deck": "<deck>",
      "macro": "<macro>",
      "value": "<value>"
    },
    "name": "set_fx_macro"
  }
}

Input Schema

Name	Required	Description	Default
`deck`	Yes
`macro`	Yes
`value`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden. It discloses the value range 0.0–1.0 but does not explain what setting a macro does, whether the macro must already exist, potential side effects, or error behavior. This is thin for a mutating operation.

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 description is short and front-loaded, with no filler. The examples and value range earn their place, though the fragment 'value 0.0–1.0' could be integrated more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three required parameters, no annotations, and no schema descriptions, the description is not sufficient. It lacks valid deck values, acceptable macro names, and guidance on how this tool relates to the many sibling FX tools.

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

Parameters3/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. It partially does by naming parameters and adding the value range and macro examples, but it leaves deck identifier format and accepted macro names underspecified.

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?

The description clearly states the action ('Set a PERF-rack macro on a deck by name') and provides concrete examples of macro names ('Glitch', 'Space', 'Crush'). It is specific about the resource, though it does not explicitly differentiate from sibling tools like set_device_parameter or fx_sweep.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives such as fx_sweep, fx_pulse, or set_device_parameter. The description only explains the mechanics, not the selection criteria or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.