Skip to main content
Glama
xDarkzx

ReaperMCP

by xDarkzx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fx_get_params

Retrieve all parameters from an FX plugin on a track, including names, values, and formatted display. Automatically filters junk parameters to keep output concise, with an optional cap for large sets.

Instructions

Get all parameters of an FX plugin (names, values, formatted display).

Automatically filters out junk params (Internal, MIDI CC, unused FabFilter bands) to keep context size small.

Args: track_index: 0-based track index, or -1 for the master track. fx_index: 0-based FX chain index. max_results: Cap on returned (post-filter) params (default 300, hard ceiling 2000) — junk filtering handles the common case (e.g. FabFilter Pro-Q's ~500 params), this is the backstop for any plugin with a genuinely large number of real params. truncated in the response says whether more exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fx_indexYes
max_resultsNo
track_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / max_results
      Added value: +{
+  "default": 300,
+  "title": "Max Results",
+  "type": "integer"
+}
  2. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does well by disclosing junk-param filtering, the default cap, the hard ceiling, and the 'truncated' response flag. It does not cover error behavior or permissions, but the main non-obvious behaviors are clearly surfaced.

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 front-loaded with the core purpose and then provides a focused Args block. The extra detail about FabFilter and the hard ceiling is useful rather than filler, though slightly longer than strictly necessary.

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?

For a read-oriented query tool with no annotations and no output schema, the description covers inputs, filtering behavior, and the truncation signal. It could specify the exact response shape more explicitly, but the essentials an agent needs to call it correctly are present.

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?

The schema has 0% description coverage, but the description fully compensates by explaining every argument: track_index zero-based with -1 for master, fx_index zero-based, and max_results with default, ceiling, and truncation semantics. This goes well beyond the raw schema.

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 a specific action and resource: get all parameters of an FX plugin with names, values, and formatted display. It clearly communicates parameter-level scope, though it does not explicitly differentiate itself from similar siblings like fx_scan_params or fx_get_chain.

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?

The description gives helpful context for max_results and explains the junk-filtering rationale, so an agent can infer when this tool is useful. However, it never explicitly says when to use this tool versus alternatives, nor does it provide any exclusion conditions or routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools