ableton-mcp

by mrinalghosh

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_track_detail

Retrieve all devices, clip slots, and routing information for a specific track in Ableton Live.

Instructions

Devices, clip slots, and routing for one 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": {
      "track": "<track>"
    },
    "name": "get_track_detail"
  }
}

Input Schema

Name	Required	Description	Default
`track`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0May 12, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the tool returns devices, clip slots, and routing, which is helpful, but it omits whether this is a read-only operation, any authorization requirements, or side effects. For a data retrieval tool, the absence of a read-only hint leaves uncertainty.

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 a single sentence that is appropriately sized and front-loaded. Every word serves a purpose with no redundant content.

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

Completeness3/5

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

Given the tool's simplicity (one integer parameter) and the existence of an output schema (so return values need not be described), the description is minimally adequate. However, it lacks details on parameter semantics and behavioral traits, leaving some ambiguity. Overall, it meets the bare minimum but has clear gaps.

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

Parameters1/5

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

The input schema has one parameter 'track' with 0% description coverage. The description adds no meaning beyond the schema's title 'Track'; it does not clarify whether the value is an index or name, or provide any format or constraints. With low schema coverage, the description should compensate but fails to do so.

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 'Devices, clip slots, and routing for one track' clearly states what the tool retrieves (devices, clip slots, routing) and for which resource (one track). It uses specific nouns and verb (implied get), distinguishing it from sibling tools like create_track or fire_clip.

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 on when to use this tool versus alternatives. While the purpose implies it's the only get-detail tool for a track, there is no explicit statement about when not to use it or mention of sibling tools like get_selected that might serve a similar purpose. The description lacks context for selection.

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

Deploy Server