Skip to main content
Glama

load_drum_kit

Load a drum rack onto a specified track and populate it with a selected drum kit from the browser to set up percussion instruments in Ableton Live.

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: 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')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
rack_uriYes
kit_pathYes

Implementation Reference

  • The handler function for the 'load_drum_kit' tool. Decorated with @mcp.tool(), which registers the tool with the MCP server. It connects to Ableton, loads a drum rack onto the specified track using the provided rack URI, retrieves drum kit items from the browser at the given kit path, selects the first loadable kit, and loads it into the rack.
    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: 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')
        """
        try:
            ableton = get_ableton_connection()
            
            # Step 1: Load the drum rack
            result = ableton.send_command("load_browser_item", {
                "track_index": track_index,
                "item_uri": rack_uri
            })
            
            if not result.get("loaded", False):
                return f"Failed to load drum rack with URI '{rack_uri}'"
            
            # Step 2: Get the drum kit items at the specified path
            kit_result = ableton.send_command("get_browser_items_at_path", {
                "path": kit_path
            })
            
            if "error" in kit_result:
                return f"Loaded drum rack but failed to find drum kit: {kit_result.get('error')}"
            
            # Step 3: Find a loadable drum kit
            kit_items = kit_result.get("items", [])
            loadable_kits = [item for item in kit_items if item.get("is_loadable", False)]
            
            if not loadable_kits:
                return f"Loaded drum rack but no loadable drum kits found at '{kit_path}'"
            
            # Step 4: Load the first loadable kit
            kit_uri = loadable_kits[0].get("uri")
            load_result = ableton.send_command("load_browser_item", {
                "track_index": track_index,
                "item_uri": kit_uri
            })
            
            return f"Loaded drum rack and kit '{loadable_kits[0].get('name')}' on track {track_index}"
        except Exception as e:
            logger.error(f"Error loading drum kit: {str(e)}")
            return f"Error loading drum kit: {str(e)}"
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool loads resources, implying a write/mutation operation, but doesn't disclose behavioral traits such as whether this requires specific permissions, if it overwrites existing content, error handling, or what happens on success (e.g., confirmation message). This leaves significant gaps for an agent to understand the tool's effects.

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 and front-loaded: the first sentence states the purpose clearly, followed by a structured parameter list. There's minimal waste, though the parameter examples could be slightly more concise. Overall, it's efficient and easy to scan.

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?

Given the complexity (a 3-parameter mutation tool with no annotations and no output schema), the description is incomplete. It lacks information on behavioral outcomes, error conditions, and how to verify success. Without annotations or output schema, the agent has insufficient context to use the tool reliably, especially for a write operation like loading resources.

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 parameters with brief examples (e.g., 'rack_uri: The URI of the drum rack to load (e.g., 'Drums/Drum Rack')'), adding meaning beyond the schema's basic titles. However, it doesn't fully explain semantics like valid ranges for 'track_index' or format details for paths, leaving some ambiguity. This partial compensation justifies a baseline score.

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 tool's purpose: 'Load a drum rack and then load a specific drum kit into it.' This specifies the verb ('load') and resources ('drum rack', 'drum kit'), making it understandable. However, it doesn't explicitly differentiate from siblings like 'load_instrument_or_effect' or 'get_browser_items_at_path', which could involve similar loading or browsing operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing track or session), exclusions, or compare to sibling tools like 'load_instrument_or_effect' for other instrument types. Usage is implied through parameter descriptions but not explicitly stated.

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/ahujasid/ableton-mcp'

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