reaper-mcp

by vecnode

Overview Schema Source Related Servers Discussions Admin

Rust

Local

track_set_solo

Solo or unsolo a specific track by its index to isolate its audio during playback.

Instructions

Solo or unsolo a track.

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>",
      "solo": "<solo>"
    },
    "name": "track_set_solo"
  }
}

Input Schema

Name	Required	Description	Default
`solo`	Yes
`track_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states the action without explaining side effects (e.g., whether solo mutes other tracks) or whether it sets or toggles the state. The boolean parameter 'solo' is not explained in context.

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?

Single, short sentence with no redundant words. Front-loaded with action and resource.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is too minimal. It omits behavior like whether solo is additive or exclusive and doesn't mention error cases for invalid track_index.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description adds no meaning beyond field names. It does not clarify that 'solo' true means enable solo and false means disable, or track_index range.

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 uses a specific action ('solo or unsolo') on a specific resource ('a track'), clearly indicating the function. It distinguishes from sibling tools like track_set_mute and track_set_volume_db by focusing on the solo state.

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?

No guidance on when to use this tool versus alternatives (e.g., track_set_mute). No context about prerequisites or limitations provided.

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