Skip to main content
Glama

item_split_at_transients

Splits an audio item at every detected transient using REAPER's native detection. Returns the resulting chops for further editing like repitch or duplicate.

Instructions

Slice an audio item at every detected transient.

Uses REAPER's native transient detection (stepping "Move cursor to next transient in items" across the item; the edit cursor is put back afterwards). Sensitivity is controlled by REAPER's project settings (Options → Preferences → Project → Item handling → Transient detection sensitivity), not by this tool — set it once in REAPER and it applies to every call.

Args: item_index: Global 0-based item index of the source audio item.

Returns: chops_created: number of new items created from the split. chops_total: total items now spanning the original time range. chops: list of {item_index, position, length, offset_in_original_sec} in playback order. The AI uses these indices to repitch / duplicate / reverse individual chops.

Input Schema

NameRequiredDescriptionDefault
item_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the native transient-detection mechanism, cursor restoration, external sensitivity settings, and return structure. It stops short of explicitly warning about destructive effects or undo behavior, which keeps it from a 5.

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 front-loaded with the core action, then provides useful behavioral detail and return values in structured Args/Returns format. The REAPER settings path is relevant context rather than filler.

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?

No output schema exists, but the description defines the return fields adequately, including chops_created, chops_total, and chop metadata. For a mutation tool with no annotations, it is nearly complete, though it could mention undo or original-item handling explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 for the single parameter. It does by defining item_index as the global 0-based index of the source audio item, which is meaningful beyond the bare schema title.

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 states a specific verb and resource: slicing an audio item at every detected transient. It clearly distinguishes this from position-based splits via the transient-detection mechanism, so an agent can identify the operation without opening the schema.

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?

It explains that the tool uses REAPER's native transient detection and that sensitivity is controlled by project settings, not by this tool. However, it does not explicitly name alternatives such as item_split or item_split_at_positions or state when to choose them.

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