Skip to main content
Glama

list_fx

Retrieve all FX plugins on a track in REAPER, including name, index, parameter count, and enabled status. Use track_index=-1 for the master track.

Instructions

List all FX plugins on a track (name, fx_index, n_params, enabled). Use track_index=-1 for the master track.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler for listing FX on a track.
    @mcp.tool()
    def list_fx(track_index: int) -> dict[str, Any]:
        """List all FX plugins on a track (name, fx_index, n_params, enabled).
        Use track_index=-1 for the master track."""
        try:
            return _wrap(adapter.list_fx(track_index=track_index))
        except Exception as exc:
            return _err(exc)
  • Adapter method that calls the bridge client to retrieve FX list.
    def list_fx(self, track_index: int) -> list[dict[str, Any]]:
        return self._client.call("list_fx", track_index=track_index)
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses the return structure (fields returned) and the special parameter value behavior (-1 for master track), but lacks information on error handling, read-only nature, or performance characteristics.

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 sentence establishes purpose and return values; second provides essential parameter semantics. Efficiently structured and appropriately sized.

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?

Appropriate for a simple read operation with existing output schema. Covers the single parameter's special case. Could be enhanced with error behavior or explicit distinction from similar FX listing tools, but sufficient for invocation.

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

Parameters4/5

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

Schema has 0% description coverage (no parameter descriptions). Description compensates by explaining the critical semantics of track_index=-1 for the master track, though it does not elaborate on valid ranges or format beyond that special case.

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?

Clearly states the tool lists FX plugins on a track and specifies what information is returned (name, fx_index, n_params, enabled). Uses specific verb and resource. Does not explicitly distinguish from sibling 'list_available_fx', though the distinction is implied by 'on a track' versus available FX.

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?

Provides specific usage guidance for accessing the master track (track_index=-1), but lacks explicit when-to-use guidance versus alternatives like 'get_fx_params' or 'list_available_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/danielkinahan/ReaMCP'

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