Skip to main content
Glama

load_instrument_or_effect

Load an instrument or effect onto a track by providing its browser URI and track index. Optionally clear existing devices before loading.

Instructions

Load an instrument or effect onto a track by its browser URI. Use get_browser_tree and get_browser_items_at_path to find URIs. Returns the loaded device_name so you can verify the correct device was loaded. Set clear_existing=true to remove all existing devices from the track before loading — recommended when replacing an instrument on a non-empty track. IMPORTANT: load instruments sequentially, not in parallel. Concurrent loads will fail or land on the wrong track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
uriYes
clear_existingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that concurrent loads fail, clear_existing removes devices, and returns device_name for verification. Does not mention auth or other constraints.

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?

Description is concise with a few sentences, front-loads main purpose, and includes important warnings at the end. Slightly could be more structured but effective.

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

Completeness4/5

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

Given moderate complexity and presence of output schema (device_name), description covers usage of clear_existing and links to browser tools. Missing differentiation from load_drum_kit but overall adequate.

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%. Description adds meaning for clear_existing (recommended for replacing instruments) but doesn't explain track_index or uri beyond their names. Some value added.

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 the tool loads an instrument or effect onto a track by URI, with a specific verb and resource. It distinguishes from siblings like load_drum_kit by being more generic.

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

Usage Guidelines4/5

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

Provides explicit usage context: use browser tools to find URIs, and warns against concurrent loads. However, it does not explicitly compare with alternatives like load_drum_kit or state when not to use.

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

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