Skip to main content
Glama
wretcher207

Reaper Daemon

by wretcher207
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

link_fx_midi_cc

Map a MIDI CC controller to any scanned FX parameter and confirm the native parameter-link readback.

Instructions

Map MIDI CC to a scanned FX parameter and verify native parameter-link readback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNo
trackNoExact track name (case-insensitive); "master" targets the master track. Used when no GUID is given; errors if two tracks share the name.
offsetNo
channelNo
dry_runNoPreview: return what would run without changing the project.
fx_guidNoStable FX GUID; wins over fx_index and fx_name_contains.
fx_indexNo0-based position in the chain; requires fx_scope "track" or "input". Used when no fx_guid is given.
fx_scopeNoWhich chain to search: "track" (normal FX), "input" (record-input FX) or "all" (default for GUID and name searches).
controllerYes
param_indexYes
track_containsNoCase-insensitive substring; used only when no GUID or exact name is given. Errors if it matches more than one track.
fx_name_containsNoCase-insensitive FX name substring; used only when neither fx_guid nor fx_index is given. Errors if it matches more than one FX.
target_track_guidNoStable REAPER track GUID; preferred when available. Wins over every other track selector.
use_selected_trackNoTarget the first selected track; ignored when any other track selector is given. Errors if nothing is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.21.0
    • addedInput schema / properties / fx_guid / description
      Added value: +"Stable FX GUID; wins over fx_index and fx_name_contains."
    • addedInput schema / properties / fx_index / description
      Added value: +"0-based position in the chain; requires fx_scope \"track\" or \"input\". Used when no fx_guid is given."
    • addedInput schema / properties / fx_name_contains / description
      Added value: +"Case-insensitive FX name substring; used only when neither fx_guid nor fx_index is given. Errors if it matches more than one FX."
    • addedInput schema / properties / fx_scope / description
      Added value: +"Which chain to search: \"track\" (normal FX), \"input\" (record-input FX) or \"all\" (default for GUID and name searches)."
    • addedInput schema / properties / fx_scope / enum
      Added value: +[
+  "all",
+  "track",
+  "input"
+]
    • changedInput schema / properties / target_track_guid / description
      Previous value: -"Stable REAPER track GUID; preferred when available."New value: +"Stable REAPER track GUID; preferred when available. Wins over every other track selector."
    • changedInput schema / properties / track / description
      Previous value: -"Exact track name (case-insensitive)."New value: +"Exact track name (case-insensitive); \"master\" targets the master track. Used when no GUID is given; errors if two tracks share the name."
    • changedInput schema / properties / track_contains / description
      Previous value: -"Case-insensitive substring; errors if it matches more than one track."New value: +"Case-insensitive substring; used only when no GUID or exact name is given. Errors if it matches more than one track."
    • changedInput schema / properties / use_selected_track / description
      Previous value: -"Target the currently selected track instead of naming one."New value: +"Target the first selected track; ignored when any other track selector is given. Errors if nothing is selected."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It mentions a verification readback, which is helpful, but it does not disclose that linking modifies project state, whether it is destructive, or what else happens beyond verification. The presence of dry_run in the schema hints at mutation, but the description does not state it.

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?

One tight sentence with no filler; the action and verification outcome are front-loaded. It is concise rather than under-specified.

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 14-parameter mutating tool with no annotations, no output schema, and rich sibling context, a single sentence is not enough. It omits side effects, prerequisites, selection precedence, and return/verification details.

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?

The description adds meaning to the two required params (controller = MIDI CC, param_index = scanned FX parameter), which lack schema descriptions. However, it does not clarify scale, offset, channel, or the track/FX selection semantics, and schema coverage at 64% leaves several params underdocumented.

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?

The description states a specific action ('Map MIDI CC to a scanned FX parameter') and adds a distinct verification behavior ('verify native parameter-link readback'). It clearly differentiates the tool from value-setting siblings like set_fx_param, though it does not explicitly name an alternative.

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 phrase 'scanned FX parameter' implies that the intended workflow is linking after a scan, and it is clear the tool is for MIDI-CC mapping rather than generic parameter editing. But there is no explicit when-to-use guidance, preconditions, or named alternatives among the many FX/MIDI sibling tools.

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