Skip to main content
Glama

simpler_sample

Load an audio sample into a Simpler device and configure playback mode, slicing, voices, warping, crop, or reverse for MIDI-triggered chops.

Instructions

Load a sample into a Simpler and set it up: playback mode (classic, one_shot, slicing), slicing by transient / beat / region / manual with sensitivity, beat division or region count (e.g. chop a break into 16 slices playable from a Drum Rack-like MIDI layout), voices, warp the sample as N beats, crop, reverse.

Parameters:

  • track_index / device_index: The Simpler

  • file_path: Absolute path of an audio file to load (optional)

  • playback_mode: classic | one_shot | slicing

  • slicing_style: transient | beat | region | manual

  • slicing_sensitivity: 0-1 (transient mode)

  • slicing_beat_division: Live's beat division index (beat mode)

  • slicing_region_count: Number of slices (region mode)

  • voices: Polyphony

  • warp_as_beats: Warp the sample to this many beats

  • crop / reverse: Destructive edits of the sample in 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>",
      "device_index": "<device_index>"
    },
    "name": "simpler_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
cropNo
voicesNo
reverseNo
file_pathNo
track_indexYes
device_indexYes
playback_modeNo
slicing_styleNo
warp_as_beatsNo
slicing_sensitivityNo
slicing_region_countNo
slicing_beat_divisionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does earn credit for flagging crop and reverse as "

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 opening sentence front-loads purpose and enumerates capabilities, then a clean bulleted parameter block follows. The parenthetical about chopping a break into 16 slices is illustrative rather than essential, and the redundant "Parameters:" heading adds little, but overall there is minimal waste.

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 exists, so return values need not be explained. But for a 12-parameter tool with zero annotation coverage and zero schema description coverage, the description leaves important gaps: mode-dependent parameter applicability, whether file_path is effectively required on first use, and the load-vs-reconfigure semantics. It is serviceable but not complete for a tool this parameterized.

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% and there are 12 parameters, so the description must compensate — and it largely does, documenting every parameter and supplying the allowed values for playback_mode and slicing_style that the schema lists as plain strings with no enums. Some entries remain thin, though: slicing_beat_division is only "Live's beat division index" with no mapping of index to musical value, voices is just "Polyphony" with no range, and there is no indication of which parameters are mutually exclusive across modes.

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?

"Load a sample into a Simpler and set it up" gives a specific verb and resource, and the following clause enumerates the configurable dimensions (playback mode, slicing style, voices, warp, crop, reverse). An agent can tell this is device-level configuration rather than clip or track creation. It stops short of naming any sibling it might be confused with, so a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only implicit routing signal is that file_path is optional, which hints the tool can either load a new file or reconfigure an already-loaded sample, but this is left for the agent to infer. Nothing tells the agent whether existing device contents are overwritten when a file_path is supplied.

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