ableton-mind

Overview Schema Source Related Servers Discussions Admin

push_set_button_led

Set the LED color and mode for Ableton Push 2/3 transport and utility buttons. Control hardware feedback after button detection.

Instructions

Set the LED color and mode for a Push transport or utility button. Use for hardware feedback after Push detection. Requires Push 2/3; defaults mode to solid and returns sent=true with the accepted button/color/mode.

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": {
      "button": "<button>",
      "color": "<color>"
    },
    "name": "push_set_button_led"
  }
}

Input Schema

Name	Required	Description	Default
`button`	Yes
`color`	Yes
`mode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description discloses hardware requirement (Push 2/3), default mode (solid), and return format (sent=true with accepted fields). It does not mention idempotency or error conditions, but is adequate for a simple LED setter.

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?

Three sentences, purpose front-loaded, no redundancy. Every sentence adds value: purpose, usage context, requirements/defaults/return. Highly efficient.

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 simple tool with 3 parameters and no output schema, the description covers purpose, usage context, hardware, defaults, and return. Missing details like color interpretation or error handling, but overall sufficient for most agents.

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 description coverage is 0%, so description must compensate. It adds context by mentioning 'LED color and mode' and the default mode, but does not explain the integer color range or the button enum options beyond the sibling context. Partial compensation leaves some ambiguity.

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 it sets LED color and mode for Push transport/utility buttons, specifying hardware feedback after Push detection. It distinguishes from siblings like push_set_pad_color and push_set_mode by targeting transport/utility buttons.

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 provides usage context ('Use for hardware feedback after Push detection') and notes hardware requirements. However, it does not explicitly state when not to use or compare to sibling tools, leaving gaps for an AI agent to decide.

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