Skip to main content
Glama

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

TableJSON Schema
NameRequiredDescriptionDefault
fx_nameYes

Implementation Reference

  • The add_master_fx tool implementation: adds an FX plugin to the master track using reapy, returns success/failure with fx_index, name, and n_params.
    def add_master_fx(fx_name: str) -> dict:
        """Add an FX plugin to the master track."""
        try:
            project = get_project()
            master = project.master_track
            fx_index = master.add_fx(fx_name)
            if fx_index < 0:
                return {"success": False, "error": f"Plugin not found: '{fx_name}'"}
            fx = master.fxs[fx_index]
            return {"success": True, "fx_index": fx_index, "name": fx.name, "n_params": fx.n_params}
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Registration of add_master_fx via @mcp.tool() decorator inside register_tools(mcp).
    def register_tools(mcp):
    
        @mcp.tool()
  • Server imports and calls register_tools from mastering_tools module to register all mastering tools including add_master_fx.
    from reaper_mcp.mastering_tools import register_tools as _reg_mastering
    from reaper_mcp.analysis_tools import register_tools as _reg_analysis
    
    _reg_project(mcp)
    _reg_track(mcp)
    _reg_midi(mcp)
    _reg_fx(mcp)
    _reg_audio(mcp)
    _reg_mixing(mcp)
    _reg_render(mcp)
    _reg_mastering(mcp)
    _reg_analysis(mcp)
  • Helper function used by add_master_fx to get the current REAPER project via reapy.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior2/5

Does 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.

Conciseness3/5

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.

Completeness2/5

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.

Parameters1/5

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.

Purpose5/5

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.

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 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bonfire-audio/reaper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server