Skip to main content
Glama

set_fx_param

Adjust audio effect parameters in REAPER projects by setting normalized values between 0.0 and 1.0 for specific tracks and effects.

Instructions

Set an FX parameter by normalized value (0.0–1.0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes
param_indexYes
normalized_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration and handler implementation for set_fx_param in the MCP server.
    @mcp.tool()
    def set_fx_param(
        track_index: int,
        fx_index: int,
        param_index: int,
        normalized_value: float,
    ) -> dict[str, Any]:
        """Set an FX parameter by normalized value (0.0–1.0)."""
        try:
            return _wrap(
                adapter.set_fx_param(
                    track_index=track_index,
                    fx_index=fx_index,
                    param_index=param_index,
                    normalized_value=normalized_value,
                )
            )
        except Exception as exc:
            return _err(exc)
  • Adapter method that forwards the set_fx_param request to the underlying REAPER client.
    def set_fx_param(
        self,
        track_index: int,
        fx_index: int,
        param_index: int,
        normalized_value: float,
    ) -> dict[str, Any]:
        return self._client.call(
            "set_fx_param",
            track_index=track_index,
            fx_index=fx_index,
            param_index=param_index,
            normalized_value=normalized_value,
        )
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully communicates the normalized value constraint (0.0–1.0), but lacks information on error handling (invalid indices), idempotency, return value structure, or whether changes are immediately applied or require additional steps.

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 is a single, well-structured sentence that front-loads the action verb and includes the essential value constraint without filler. Every word earns its place.

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 zero schema coverage and no annotations, the description is insufficient for a 4-parameter addressing tool. While the output schema covers returns, the input parameters (especially the three indices) require documentation that is missing here.

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 coverage is 0%, requiring the description to compensate. It adds critical semantic information for normalized_value (the 0.0–1.0 range), but provides no guidance for track_index, fx_index, or param_index (e.g., zero-indexed vs one-indexed, valid ranges), leaving three of four parameters undocumented.

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 states the specific action ('Set') and resource ('FX parameter'), and distinguishes itself from siblings like get_fx_params or set_fx_enabled by specifying the mechanism ('by normalized value'). However, it could more explicitly contrast with set_fx_preset to clarify this manipulates individual parameters versus loading presets.

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?

The description provides no guidance on when to use this tool versus alternatives like set_fx_preset or how to determine valid indices. It only states what the tool does, not when to prefer it over other FX manipulation tools in the sibling list.

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