Skip to main content
Glama

set_fx_parameter

Adjust any FX plugin parameter by setting a normalized value between 0.0 and 1.0. Use parameter indices obtained from get_fx_parameters to target specific parameters.

Instructions

Set a normalized parameter value (0.0–1.0) on an FX plugin. Use get_fx_parameters to discover available parameters and their indices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes
param_indexYes
valueYes

Implementation Reference

  • The handler function for the set_fx_parameter tool. Decorated with @mcp.tool(), it sets a normalized parameter value (0.0–1.0) on an FX plugin at the given track/fx/param indices.
    @mcp.tool()
    def set_fx_parameter(
        track_index: int, fx_index: int, param_index: int, value: float
    ) -> dict:
        """
        Set a normalized parameter value (0.0–1.0) on an FX plugin.
        Use get_fx_parameters to discover available parameters and their indices.
        """
        try:
            project = get_project()
            track = project.tracks[track_index]
            fx = track.fxs[fx_index]
            fx.params[param_index].normalized_value = value
            param_name = fx.params[param_index].name
            return {
                "success": True,
                "track_index": track_index,
                "fx_index": fx_index,
                "param_index": param_index,
                "param_name": param_name,
                "value": value,
            }
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Type-annotated input schema for set_fx_parameter: track_index (int), fx_index (int), param_index (int), value (float). Return type is dict.
    def set_fx_parameter(
        track_index: int, fx_index: int, param_index: int, value: float
    ) -> dict:
  • The tool is registered in server.py by importing register_tools from fx_tools.py and calling it with the mcp instance. Inside fx_tools.py, the @mcp.tool() decorator on set_fx_parameter registers it.
    from reaper_mcp.fx_tools import register_tools as _reg_fx
    from reaper_mcp.audio_tools import register_tools as _reg_audio
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
    from reaper_mcp.render_tools import register_tools as _reg_render
    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)
  • Helper function used by set_fx_parameter to obtain the current REAPER project via reapy.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior3/5

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

Without annotations, the description carries the full burden. It adds important behavioral info: the value must be normalized (0.0–1.0). However, it does not disclose error behavior, destructive potential, or permission requirements. The value range is useful but incomplete.

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?

The description consists of two short, front-loaded sentences. Every word adds value: the purpose and a usage hint. No filler, perfectly concise.

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 4-parameter tool with no output schema and no annotations, the description covers the core intent and one parameter detail (value range). It omits return value information and error handling. Adequate but not thorough.

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 description coverage is 0%, so the description must compensate. It clarifies the 'value' parameter as a normalized range (0.0–1.0), but does not describe track_index, fx_index, or param_index. Their names are somewhat self-explanatory but lack explicit context.

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 action: 'Set a normalized parameter value (0.0–1.0) on an FX plugin'. It specifies the resource (FX plugin) and the verb (set), and distinguishes from siblings like set_master_fx_parameter and get_fx_parameters.

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 explicitly advises using get_fx_parameters to discover parameters and indices, providing clear contextual guidance. It does not list when not to use the tool or alternatives, but the sibling tools imply different scopes (master vs track FX).

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