Skip to main content
Glama

list_available_fx

Discover and filter installed audio effects plugins (VST, VST3, CLAP, JS) in REAPER projects to identify available processing tools for your mix.

Instructions

List installed FX plugins (VST, VST3, CLAP, and JS/JSFX).

  • filter: optional case-insensitive substring to match against plugin name or type e.g. 'fabfilter', 'vst3', 'clap', 'rea', 'comp' Returns a list of {name, type} objects and a total count. type values: 'VST' (VST2), 'VST3', 'CLAP', 'JS'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool registration and handler implementation for list_available_fx.
    @mcp.tool()
    def list_available_fx(filter: str | None = None) -> dict[str, Any]:
        """
        List installed FX plugins (VST, VST3, CLAP, and JS/JSFX).
        - filter: optional case-insensitive substring to match against plugin name or type
                  e.g. 'fabfilter', 'vst3', 'clap', 'rea', 'comp'
        Returns a list of {name, type} objects and a total count.
        type values: 'VST' (VST2), 'VST3', 'CLAP', 'JS'
        """
        try:
            return _wrap(adapter.list_available_fx(filter=filter))
        except Exception as exc:
            return _err(exc)
  • Adapter method that forwards the call to the underlying Reaper client.
    def list_available_fx(
        self, filter: str | None = None
    ) -> dict[str, Any]:
        return self._client.call("list_available_fx", filter=filter)
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 documents the return format ({name, type} objects with total count) and filter matching logic (case-insensitive substring against name/type). However, it omits safety context (read-only nature, performance characteristics of scanning plugins) that annotations would typically cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with clear structure: purpose statement, bullet-point parameter details with examples, and return value specification. No wasted words, though the return value description could be slightly more integrated.

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 the tool has one optional parameter and an output schema, the description provides sufficient completeness by explaining the return structure and enumerating valid type values ('VST', 'VST3', 'CLAP', 'JS'). Missing only explicit differentiation from the 'list_fx' sibling.

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

Parameters5/5

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

Schema description coverage is 0%, but the description excellently compensates by documenting the 'filter' parameter in detail: it is optional, case-insensitive, matches against plugin name or type, and provides concrete examples ('fabfilter', 'vst3', 'clap', 'rea', 'comp').

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 specifies the verb (List), resource (installed FX plugins), and supported formats (VST, VST3, CLAP, JS). However, it does not distinguish from the sibling tool 'list_fx', which likely lists active FX instances on tracks rather than available system plugins.

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 is provided on when to use this tool versus alternatives like 'list_fx' or how it relates to 'add_fx'. There are no prerequisites, exclusion criteria, or workflow positioning hints.

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