Skip to main content
Glama
Sign In
Ableton MCP Extended

Ableton MCP Extended

by zabolotniydj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_drum_kit

Load a drum rack onto a specified track, then populate it with a chosen drum kit from the browser. Enables quick setup of drum sounds for production.

Instructions

Load a drum rack and then load a specific drum kit into it.

Parameters:

  • track_index: Track number (1-based).

  • rack_uri: The URI of the drum rack to load (e.g., 'Drums/Drum Rack').

  • kit_path: Path to the drum kit inside the browser (e.g., 'drums/acoustic/kit1').

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_index": "<track_index>",
      "rack_uri": "<rack_uri>",
      "kit_path": "<kit_path>"
    },
    "name": "load_drum_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_pathYes
rack_uriYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

The description only states the direct action without detailing side effects, permissions, error conditions, or reversibility. It does not disclose whether the operation modifies the session in a way that could require cleanup or have undo implications.

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, clear sentence with no unnecessary words. The structure is direct and effective.

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?

While the action and parameters are clear, the description lacks contextual information about when to use this tool compared to similar loading tools like load_instrument_or_effect. It is adequate for a simple operation but incomplete in guiding selection among alternatives.

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

Parameters5/5

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

All three parameters have precise descriptions in the schema: track_index (1-based), rack_uri (example given), and kit_path (example given). The descriptions fully clarify the expected inputs, making the schema self-sufficient.

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 what the tool does: loads a drum rack and then a specific drum kit into it. It is specific and distinguishes from sibling tools like load_instrument_or_effect.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or when it is appropriate. The agent is left to infer usage from the description alone.

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