Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by rephlex187
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_track_mute

Mute or unmute a specific track in Ableton Live by specifying its index and the mute state.

Instructions

Mute or unmute a track.

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": {
      "ctx": "<ctx>",
      "track_index": "<track_index>",
      "mute": "<mute>"
    },
    "name": "set_track_mute"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxYes
muteYes
track_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description must convey behavioral traits. It states 'mute or unmute,' implying a mutation, but offers no details on required permissions, effects on playback, or reversibility. It does not address edge cases like muting an already muted track.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it lacks structure. It could be front-loaded with purpose but is too brief to be informative. It earns its space but provides no additional value.

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

Completeness1/5

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

Given the lack of annotations, output schema, and parameter descriptions, combined with the complexity of a DAW environment, the description is severely incomplete. It does not explain return values, track selection context, or relation to other track operations. The agent is left with minimal guidance.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for parameters. The description adds no meaning beyond parameter names. 'track_index' is ambiguous (0-based vs 1-based), and 'mute' as a boolean is not explained. The agent must infer from names alone.

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 'Mute or unmute a track' clearly specifies the action (mute/unmute) and the resource (track). It uses a specific verb and resource, and is distinguishable from sibling tools like set_track_solo or set_track_volume. However, it does not differentiate from other track state setters, which is acceptable for such a common operation.

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 guidelines are provided regarding when to use this tool versus alternatives. There is no mention of prerequisites, track existence, or relationship to other mute-related tools. The description fails to aid the agent in deciding to use this tool over similar ones like set_track_arm or set_track_solo.

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