add_master_fx
Add a specified FX plugin to the master track for global audio processing in REAPER.
Instructions
Add an FX plugin to the master track.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fx_name | Yes |
Add a specified FX plugin to the master track for global audio processing in REAPER.
Add an FX plugin to the master track.
| Name | Required | Description | Default |
|---|---|---|---|
| fx_name | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It only states the basic action, omitting details like whether it inserts at end, replaces, or any prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise at one sentence, but this brevity sacrifices essential detail. It is front-loaded but under-informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (1 required param), the description is incomplete. It does not explain the parameter or provide minimal context for use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and parameter 'fx_name' lacks description. The tool description provides no additional meaning, format, or examples for the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Add' and the resource 'FX plugin to the master track', which distinguishes it from sibling tool 'add_fx' that likely adds to regular tracks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like 'add_fx' or conditions for use. The description does not provide any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.