Skip to main content
Glama

get_fx_params

Retrieve all parameters for an FX plugin on a track in REAPER, including index, name, value ranges, and normalized data for audio project management.

Instructions

Return all parameters for an FX plugin on a track. Each entry includes: param_index, name, value, min_value, max_value, normalized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for "get_fx_params" in the MCP server. It wraps calls to the ReaperAdapter.
    def get_fx_params(track_index: int, fx_index: int) -> dict[str, Any]:
        """
        Return all parameters for an FX plugin on a track.
        Each entry includes: param_index, name, value, min_value, max_value, normalized.
        """
        try:
            return _wrap(adapter.get_fx_params(track_index=track_index, fx_index=fx_index))
        except Exception as exc:
            return _err(exc)
  • The ReaperAdapter implementation, which acts as a client to communicate with the REAPER Lua bridge.
    def get_fx_params(
        self,
        track_index: int,
        fx_index: int,
    ) -> list[dict[str, Any]]:
        return self._client.call(
            "get_fx_params",
            track_index=track_index,
            fx_index=fx_index,
        )
Behavior4/5

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

No annotations provided, so description carries full disclosure burden. It successfully indicates this is a read-only operation ('Return') and crucially documents the output structure ('Each entry includes: param_index, name...'), providing transparency into return format. Missing explicit error conditions or indexing conventions.

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?

Two sentences with zero waste: first states purpose, second documents return structure. Every word earns its place. Appropriate density for a simple getter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given existence of output schema, description appropriately focuses on high-level purpose while still previewing return structure (param_index, normalized values, etc.). Complete for a 2-parameter read operation, though could mention indexing conventions or valid ranges for full marks.

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 has 0% description coverage (only titles 'Track Index', 'Fx Index'). Description compensates by establishing semantic context: 'FX plugin on a track' maps the indices to their domain entities. However, lacks specifics on indexing scheme (0-based vs 1-based), valid ranges, or parameter constraints that would fully compensate for absent schema descriptions.

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?

Description uses specific verb 'Return' with clear resource 'all parameters for an FX plugin' and scope 'on a track'. Effectively distinguishes from siblings: contrasts with set_fx_param (single parameter mutation), list_fx (listing plugins not parameters), and add_fx/remove_fx (plugin management).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit 'when to use' guidance or alternative recommendations provided. However, usage is reasonably implied by the descriptive output format (enumerating return fields), suggesting this is for inspection/introspection of plugin state before modification.

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