Skip to main content
Glama

wipe_all_midi

Remove all MIDI items from chosen tracks or the whole project, keeping audio untouched. Reset composition state so tracks can record anew; full wipe also clears markers and regions.

Instructions

Wipe all MIDI items and reset composition state. Tracks can compose again after.

Only deletes items whose active take is MIDI — audio items on the same tracks are left untouched. On a full wipe (tracks omitted), also clears all markers and regions.

Args: tracks: JSON array of track indices e.g. "[0,1,2]", or empty for all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tracksNo
Behavior4/5

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

No annotations exist, so description carries full burden. Describes destructive behavior, selective deletion by active take type, and side effect on markers/regions. Missing details on permissions, undoability, or rate limits.

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?

Very concise: 4 short sentences plus args section. No wasted words, front-loaded with main action.

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

Completeness5/5

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

For a tool with one parameter, no output schema, and low complexity, the description fully covers purpose, behavior, and parameter semantics.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'tracks' is fully explained: it's a JSON array of track indices, with example and meaning of empty string. Schema coverage is 0%, but description compensates excellently.

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?

Clearly states the tool wipes all MIDI items and resets composition state. Distinguishes from siblings by specifying it only affects MIDI items with active MIDI takes, leaving audio untouched. The verb 'wipe' and resource 'MIDI items' are specific.

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 clear context on when to use: when wiping MIDI items while preserving audio. Describes side effect of full wipe clearing markers/regions. Lacks explicit when-not to use or mention of alternatives among siblings.

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/xDarkzx/Reaper-MCP'

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