messier-live

by maramasaeva

Overview Schema Source Related Servers Discussions Admin

Python

Local

Eq Kill

eq_kill

Kill or restore a low, mid, or high EQ band on a deck in Ableton Live, requiring an EQ Three device on the track.

Instructions

Kill (or restore) an EQ band on a deck. Needs an 'EQ Three' device on the deck track. band: low | mid | high.

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>"
    },
    "name": "eq_kill"
  }
}

Input Schema

Name	Required	Default
`band`	No	low
`deck`	Yes
`restore`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations available, the description carries the burden of explaining behavior. It discloses that the tool mutates state by killing or restoring an EQ band and mentions the device requirement, but it does not explain consequences such as whether killing nullifies the band, whether restore is a true inverse, or what happens if the required device is absent.

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 extremely concise: two sentences with no filler. The primary action is front-loaded, and the prerequisite and band values are stated efficiently in the second sentence.

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 three-parameter tool with an output schema, this is nearly complete. It covers the operation, prerequisite, and allowed band values. The only notable gap is the undefined 'deck' parameter format, which is a minor omission given the other contextual clues.

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 the description must compensate. It explicitly defines band as 'low | mid | high' and implies the restore behavior, but the 'deck' parameter remains purely a string with no format or identification guidance, and the mapping of the 'restore' boolean to kill/restore is only implicit.

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 states a specific verb ('Kill (or restore)') and a specific resource ('an EQ band on a deck'), which clearly identifies the tool's function. It also differentiates it from sibling tools like kill_all_fx by narrowing the scope to a single EQ band on a single deck.

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 clear context by stating the prerequisite condition: an 'EQ Three' device must be on the deck track. It does not explicitly name alternative tools or exclusion criteria, but the prerequisite is enough to guide when this tool is applicable.

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