messier-live

Overview Schema Source Related Servers Discussions Admin

Load To Deck

load_to_deck

Load an audio file into a deck's clip slot in Ableton Live without starting playback. Assign the file to a chosen deck and clip slot to prepare tracks for live performance.

Instructions

Load an audio file into a deck's clip slot (does not start playback).

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": {
      "deck": "<deck>",
      "file_path": "<file_path>"
    },
    "name": "load_to_deck"
  }
}

Input Schema

Name	Required	Description	Default
`deck`	Yes
`file_path`	Yes
`clip_index`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It usefully discloses that playback will not start, but it does not mention potential side effects such as overwriting an existing clip, deck readiness requirements, or error behavior.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no filler. The key behavior and the important non-behavior are both stated efficiently.

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?

The tool is simple, and the description covers the core action and the non-playback guarantee. However, it omits context about overwriting behavior and clip_index semantics, which an agent might need to invoke it safely in a real session.

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 add meaning. It does map 'audio file' to file_path, 'deck' to deck, and 'clip slot' to clip_index, but it provides no details about valid formats, index range, or how the default clip_index behaves.

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 names a specific verb ('Load') and resource ('audio file into a deck's clip slot'), and the parenthetical 'does not start playback' distinguishes it from playback-oriented siblings like play and fire_deck. This gives an agent a clear, unambiguous function.

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?

The description makes the intended use clear: load an audio file without triggering playback. It implies when to choose this tool over playback tools, though it does not explicitly name alternatives or state when not to use it beyond the playback exclusion.

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