Skip to main content
Glama

load_drum_kit

Load drum kits into Ableton Live tracks by specifying track index, rack URI, and kit path to create drum patterns for music production.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
rack_uriYes
kit_pathYes

Implementation Reference

  • The handler function for the load_drum_kit tool. It first loads a drum rack onto the specified track using the provided rack_uri. Then, it fetches items at the specified kit_path in the browser, selects the first loadable drum kit, and loads it onto the track. Returns a success or error message.
    @mcp.tool()
    def load_drum_kit(ctx: Context, track_index: int, rack_uri: str, kit_path: str) -> str:
        try:
            ableton = get_ableton_connection()
            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}'"
            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')}"
            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}'"
            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)}"
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/Milesy1/MCP-Ableton-API'

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