Skip to main content
Glama

load_instrument_or_effect

Load instruments or effects onto Ableton Live tracks using URI identifiers to configure audio production setups.

Instructions

Load an instrument or effect onto a track using its URI.

Parameters:

  • track_index: The index of the track to load the instrument on

  • uri: The URI of the instrument or effect to load

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
uriYes

Implementation Reference

  • The handler function that registers the 'load_instrument_or_effect' tool and invokes the internal 'load_browser_item' command.
    @mcp.tool()
    def load_instrument_or_effect(ctx: Context, track_index: int, uri: str) -> str:
        """
        Load an instrument or effect onto a track using its URI.
    
        Parameters:
        - track_index: The index of the track to load the instrument on
        - uri: The URI of the instrument or effect to load
        """
        try:
            result = _run("load_browser_item", {
                "track_index": track_index,
                "item_uri": uri
            })
            if result.get("loaded", False):
                devices = result.get("new_devices") or result.get("devices_after", [])
                return f"Loaded '{uri}' on track {track_index}. Devices: {', '.join(devices)}"
            return f"Failed to load '{uri}'"
        except Exception as e:
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It states the action but doesn't disclose effects (e.g., overwrites existing instrument, requires valid URI format, may affect playback, or has no return value). This leaves gaps for a mutation tool with zero annotation coverage.

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 front-loaded with the core purpose, followed by a parameter list. It's efficient with two sentences, though the parameter section could be integrated more smoothly. No redundant information, but slightly fragmented structure.

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 mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on behavior, error conditions, return values, and context relative to siblings. More is needed given the complexity and missing structured data.

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 and briefly explains 'track_index' and 'uri', but adds minimal semantics beyond schema titles (e.g., no format for URI, track index range, or examples). It partially addresses the coverage gap but not comprehensively.

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') and resource ('instrument or effect onto a track'), specifying it uses a URI. It distinguishes from siblings like 'load_drum_kit' by being generic for instruments/effects, but doesn't explicitly contrast with other track-related tools like 'create_midi_track' or 'set_track_name'.

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 is provided. It doesn't mention prerequisites (e.g., track existence), differentiate from 'load_drum_kit' (which might be a subset), or specify contexts like during playback vs. editing. Usage is implied but not articulated.

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