Skip to main content
Glama

load_drum_kit

Load a drum rack and specific drum kit into Ableton Live tracks for music production. Use this tool to configure drum sounds by specifying track index, rack URI, and kit path.

Instructions

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

Parameters:

  • track_index: The index of the track to load on

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

  • kit_path: Browser path to the drum kit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
rack_uriYes
kit_pathYes

Implementation Reference

  • The implementation of the load_drum_kit tool which orchestrates loading a drum rack and a kit into a specified track.
    @mcp.tool()
    def load_drum_kit(ctx: Context, track_index: int, rack_uri: str, kit_path: str) -> str:
        """
        Load a drum rack and then load a specific drum kit into it.
    
        Parameters:
        - track_index: The index of the track to load on
        - rack_uri: URI of the drum rack (e.g. 'Drums/Drum Rack')
        - kit_path: Browser path to the drum kit
        """
        try:
            result = _run("load_browser_item", {
                "track_index": track_index,
                "item_uri": rack_uri
            })
            if not result.get("loaded", False):
                return f"Failed to load drum rack '{rack_uri}'"
    
            kit_result = _run("get_browser_items_at_path", {"path": kit_path})
            if "error" in kit_result:
                return f"Drum rack loaded but kit not found: {kit_result.get('error')}"
    
            loadable = [i for i in kit_result.get("items", []) if i.get("is_loadable")]
            if not loadable:
                return f"Drum rack loaded but no loadable kits at '{kit_path}'"
    
            kit = loadable[0]
            _run("load_browser_item", {
                "track_index": track_index,
                "item_uri": kit.get("uri")
            })
            return f"Loaded drum rack + kit '{kit.get('name')}' on track {track_index}"
        except Exception as e:
            return f"Error loading drum kit: {e}"
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read/write operation, permission requirements, side effects, or what happens on success/failure. The description is minimal and lacks necessary context for safe invocation.

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

Conciseness4/5

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

The description is appropriately sized with a clear purpose statement followed by parameter listings. It's front-loaded and wastes no words, though the parameter section could be integrated more smoothly.

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

Completeness2/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the description is incomplete. It lacks information about return values, error conditions, and behavioral details needed for reliable use in a DAW context. The purpose is clear, but operational context is missing.

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 lists all three parameters with brief examples ('e.g. 'Drums/Drum Rack'') but doesn't explain their semantics deeply (e.g., what track_index refers to, format of kit_path). It adds some value but doesn't fully bridge the coverage gap.

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 clearly states the action ('Load a drum rack and then load a specific drum kit into it') with specific verbs and resources. It distinguishes itself from siblings like 'load_instrument_or_effect' by focusing on drum kits specifically, though it doesn't explicitly contrast with that sibling.

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 like 'load_instrument_or_effect' or 'get_browser_items_at_path'. The description implies usage for drum kit loading but lacks context about prerequisites, timing, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FreeRiverHouse/ableton-flow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server