Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

remove_fx

Delete an FX plugin from a track's effects chain in REAPER. Specify track and FX indices to remove specific audio processing tools from your project.

Instructions

Remove an FX plugin from a track's FX chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:551-557 (handler)
    The MCP tool definition and handler for 'remove_fx'. It wraps the adapter call and handles potential errors.
    @mcp.tool()
def remove_fx(track_index: int, fx_index: int) -> dict[str, Any]:
    """Remove an FX plugin from a track's FX chain."""
    try:
        return _wrap(adapter.remove_fx(track_index=track_index, fx_index=fx_index))
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:315-318 (helper)
    The adapter method that forwards the 'remove_fx' request to the REAPER client.
    def remove_fx(self, track_index: int, fx_index: int) -> dict[str, Any]:
    return self._client.call(
        "remove_fx", track_index=track_index, fx_index=fx_index
    )

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It states 'Remove' implying destruction, but fails to disclose whether the action is undoable, if automation data for the FX is deleted, or what occurs if indices are invalid (exception vs silent failure).

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 a single, efficiently structured sentence with no redundancy. However, given the 0% schema coverage and destructive nature of the operation, this brevity is inadequate; the description is under-specified rather than appropriately concise.

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?

Despite having an output schema (reducing the need to describe return values), the description is insufficient for a destructive mutation tool with zero input schema documentation. It lacks error behavior, parameter validation details, and side-effect disclosure expected when annotations are absent.

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?

Schema description coverage is 0%—neither parameter has a description field. While the single sentence implies track_index identifies the track and fx_index identifies the plugin position, it does not explain indexing schemes (0-based vs 1-based) or valid ranges, which is critical information for integer indices in audio software.

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 uses a specific verb (Remove) with clear resource (FX plugin) and scope (track's FX chain). However, it does not explicitly distinguish this permanent deletion from the sibling tool set_fx_enabled (which presumably bypasses/disables without removing), a critical distinction in DAW workflows.

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 provided on when to use this versus alternatives (e.g., set_fx_enabled for temporary bypass), nor prerequisites (e.g., track/FX must exist). The agent must infer usage solely from the verb.

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/danielkinahan/ReaMCP'

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