Skip to main content
Glama
bonfire-systems

REAPER MCP Server

by bonfire-systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_stems

Render selected or all tracks as separate stem files by soloing each track and saving outputs named after track names in the output directory.

Instructions

Render each track as a separate stem file by soloing each track individually. track_indices: list of track indices, or null to render all tracks. Files are named after the track names in the output directory.

Input Schema

NameRequiredDescriptionDefault
formatNowav
bit_depthNo
sample_rateNo
track_indicesNo
output_directoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • addedInput schema / properties / track_indices / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / track_indices / items
      Removed value: -{}
    • removedInput schema / properties / track_indices / type
      Removed value: -"array"
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the solo-per-track mechanism and the file-naming convention, but does not say whether solo state is restored afterwards, whether rendering overwrites existing files, or whether the operation is realtime/long-running - significant gaps for a mutation-plus-file-write tool.

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?

Three short sentences, front-loaded with the core behavior, then parameter semantics, then output convention - no filler whatsoever.

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?

For a 5-parameter render tool with no annotations and no output schema, the description covers the essential behavior, subset selection and file naming; what is missing (solo-state restoration, per-file format details, what the call returns) is modest given the sibling render tools cover similar ground.

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 compensate. It clarifies the non-obvious track_indices parameter (null = all tracks) and implicitly the output_directory via file naming, but format, bit_depth and sample_rate are only self-describing names with schema defaults and get no guidance from the description.

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?

States a specific verb (render) and a specific output artifact (separate stem file per track), plus the mechanism used ('soloing each track individually'), which inherently distinguishes it from siblings like render_project, render_regions and render_time_selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The null-vs-list semantics for track_indices implies when to render a subset versus everything, but the description never says when to choose this tool over render_project or render_regions, nor any prerequisites (e.g. tracks must exist, project must be loaded).

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