Skip to main content
Glama

add_master_fx

Add FX plugins to the master track in REAPER DAW for final mix processing and mastering workflows.

Instructions

Add an FX plugin to the master track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fx_nameYes

Implementation Reference

  • The add_master_fx tool implementation. Decorated with @mcp.tool(), this function adds an FX plugin to the master track by name. It retrieves the project via get_project(), accesses the master track, adds the FX, and returns success status with FX metadata (index, name, n_params) or an error if the plugin is not found.
    @mcp.tool()
    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)}
  • MCP tool registration via decorator. The @mcp.tool() decorator registers add_master_fx as an available tool in the MCP server, exposing it to clients.
    @mcp.tool()
Behavior2/5

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

No annotations provided and description fails to disclose behavioral details like whether FX is appended/prepended to chain, error handling for invalid names, or if it replaces existing plugins.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is appropriately front-loaded and not verbose, though extreme brevity limits utility given lack of supporting schema documentation.

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?

Covers basic purpose but leaves critical gaps regarding parameter constraints and operation behavior, minimally viable for a simple tool but missing expected context for 'fx_name' enumeration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must explain 'fx_name' format/valid values, but provides no guidance on acceptable inputs, casing, or how to discover available plugin names.

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?

States specific action (Add) and target (FX plugin to master track), clearly distinguishing from sibling 'add_fx' by specifying 'master track', though 'FX plugin' could be more specific (VST/AU/etc.).

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?

Provides no guidance on when to use this versus 'add_fx', 'apply_mastering_chain', or 'set_master_fx_parameter', nor when not to use it.

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