Skip to main content
Glama
Sign In
reaper-mcp

reaper-mcp

by T-Rzeznik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reaper_list_fx_params

Read-onlyIdempotent

List an FX's parameters with their current value, minimum, and maximum to read plugin-native values before making adjustments.

Instructions

List an FX's parameters with current value, min, and max.

Returns a list of {index, name, value, min, max}. Parameter values are plugin-native (often normalised 0..1) — read min/max before setting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "fx_index": "<fx_index>"
    },
    "name": "reaper_list_fx_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes0-based track index
fx_indexYes0-based FX index within the track chain
response_formatNo'markdown' for human-readable output or 'json' for machine-readablemarkdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable context about plugin-native values often being normalized 0..1 and advises reading min/max before setting, which goes beyond the annotations.

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 concise with two sentences, no wasted words. It front-loads the core purpose and then adds necessary context about return format and value normalization.

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 that an output schema is reported to exist (though not shown), the description adequately explains the return structure and behavioral nuance. It could mention potential errors or limitations, but for a simple list tool, it is sufficiently complete.

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 coverage is 100%, so the schema already documents all parameters. The description does not add further meaning to the parameters themselves (track_index, fx_index, response_format) beyond the schema, but it does explain the return format, which is not directly about parameters.

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?

The description clearly states it lists FX parameters with current value, min, and max. It distinguishes from sibling tools like reaper_list_track_fx (lists FX on a track) and reaper_set_fx_param (sets parameters), making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description implicitly advises usage by stating 'read min/max before setting', implying this tool is a precursor to reaper_set_fx_param. However, it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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