Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_sample

Destructive

Load an audio sample into Simpler on a specified Ableton Live track from a browser query/URI, or replace an existing track's sample using a WAV/AIFF file path.

Instructions

Put a sample into Simpler. query/uri: from Live's browser onto the track (an empty MIDI track gets a new Simpler). path: a .wav/.aif on disk replaces the sample in the track's existing Simpler.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>"
    },
    "name": "load_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriNo
pathNo
queryNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing consequences: a path load replaces the existing sample inside the track's Simpler, while a browser load onto an empty MIDI track creates a new Simpler. That mutation detail matters given destructiveHint=true. It does not state what happens if path is used on a track with no Simpler, or how conflicts between query/uri/path are resolved.

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?

Purpose first, then parameter-mode semantics in a compact pair of clauses; no filler. The fragmentary 'query/uri: ... path: ...' phrasing is terse to the point of being slightly cryptic, but it stays front-loaded and short.

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

Completeness3/5

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

An output schema and annotations are present, so return values and safety are covered elsewhere. Missing from the description are the things only it can supply: how the three optional source parameters interact, and behavior when the target track lacks a Simpler or does not exist.

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 coverage is 0%, so the description must carry parameter meaning, and it only partly does. It explains query/uri as browser sources and path as a disk file, but never clarifies the distinction between query (search) and uri (direct identifier), track_index semantics (must the track already exist, MIDI vs audio), or mutual exclusivity/precedence among the three source parameters.

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?

States a specific verb and resource: putting a sample into a Simpler on a given track, with two source modes distinguished. It is clearly different from siblings like load_drum_kit or load_plugin, though it never names those alternatives.

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?

Gives usable routing guidance between the two input modes: browser query/uri for Live's browser content, disk path for .wav/.aif files. It does not say when to prefer a sibling tool such as load_browser_uri or set_simpler, and gives no preconditions.

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

Deploy Server

Other Tools