reaper-reapy-mcp

by wegitor

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_fx_list

Retrieve all effects (FX) on a specified track by using its track index.

Instructions

Get a list of all FX on a track.

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>"
    },
    "name": "get_fx_list"
  }
}

Input Schema

Name	Required	Description	Default
`track_index`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden. It does not disclose behavioral details such as whether the returned list includes disabled FX, the order of FX, or what error occurs if the track_index is invalid. The description adds minimal context beyond the tool name.

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 a single, clear sentence with no redundant words. It is appropriately sized for the tool's simplicity and front-loads the essential purpose.

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 simple nature of the tool (one parameter, output schema available), the description is mostly complete. It clearly states the action and object. However, it lacks explicit guidance on prerequisites or relationship to sibling tools, slightly reducing completeness.

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

Parameters2/5

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

Schema description coverage is 0% and the description does not mention the track_index parameter. The schema only provides type and required flag, leaving ambiguities like zero-based indexing and how to obtain a valid index (e.g., from get_track_list) undocumented.

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 'Get a list of all FX on a track' with a specific verb (Get) and resource (FX on a track). It distinguishes this from sibling tools like get_available_fx_list (which lists available plugins) and get_fx_param_list (which lists parameters).

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 get_available_fx_list or get_fx_param_list. The description only states what the tool does, leaving the use case implied but not explicit.

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