Skip to main content
Glama
wretcher207

Reaper Daemon

by wretcher207
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_fx_preset

Loads a specific REAPER FX preset by exact name and verifies readback to confirm the preset applied correctly.

Instructions

Load an exact REAPER host preset name and verify readback. Proprietary preset files may require plugin UI; saved chains use add_fx_chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
trackNoExact track name (case-insensitive); "master" targets the master track. Used when no GUID is given; errors if two tracks share the name.
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).
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

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses verification behavior and a plugin-UI dependency, but it does not state whether the operation mutates the project, what happens on failed readback, or whether it is reversible.

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?

Two short sentences front-load the primary action and include a high-value caveat and sibling route without filler.

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

Completeness3/5

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

For a 10-parameter tool with no annotations or output schema, the description is thin on overall behavior: it hints at 'verify readback' but not the return value, mutation/safety profile, or failure semantics. The rich schema covers parameters, so the description is minimally viable but leaves notable gaps.

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 coverage is 90%, so the parameter descriptions in the schema already carry most semantic weight. The description adds only 'exact' matching and the saved-chain distinction; it contributes no additional parameter-level detail.

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 action ('Load an exact REAPER host preset name') and an observable outcome ('verify readback'), which clearly distinguishes it from get-oriented and chain-insertion siblings. It also names add_fx_chain as the tool for saved chains, reinforcing scope.

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?

The description gives a concrete exclusion ('saved chains use add_fx_chain') and a caveat for proprietary preset files, which helps an agent route to an alternative. It does not explicitly spell out when to prefer this over get_fx_preset, but set vs. get is clear from the name.

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