Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

set_project_parameter

Configure project settings like loop boundaries, cursor position, and playback speed in REAPER to customize audio project behavior.

Instructions

Set a named project parameter. Supported parameters: loop_start, loop_end, loop_enabled, cursor_position, playrate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parameterYes
valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:640-649 (handler)
    The MCP tool handler for 'set_project_parameter' that delegates to the reaper adapter.
    @mcp.tool()
def set_project_parameter(parameter: str, value: Any) -> dict[str, Any]:
    """
    Set a named project parameter.
    Supported parameters: loop_start, loop_end, loop_enabled, cursor_position, playrate
    """
    try:
        return _wrap(adapter.set_project_parameter(parameter=parameter, value=value))
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:372-377 (handler)
    The underlying adapter method that performs the actual RPC call to the REAPER client.
    def set_project_parameter(self, parameter: str, value: Any) -> dict[str, Any]:
    return self._client.call(
        "set_project_parameter",
        parameter=parameter,
        value=value,
    )

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It successfully defines the valid parameter domain via the supported list, but lacks information on validation behavior, atomicity, side effects on playback, or failure modes when invalid values are provided.

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 declares purpose, second lists valid inputs. Every word earns its place. Appropriate density for a simple setter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has output schema (exempting return value documentation) and only 2 parameters, but the 'value' parameter remains semantically opaque despite being critical for successful operation. Missing behavioral context expected for a state-mutation tool with no annotations.

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. The description compensates significantly by enumerating valid values for the 'parameter' argument (loop_start, loop_end, etc.), acting as implicit documentation for what would typically be an enum. However, it completely omits type/format expectations for the 'value' parameter (e.g., numeric vs boolean, time formats).

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?

States specific verb (Set) and resource (project parameter) and distinguishes scope by listing five supported parameter names (loop_start, loop_end, etc.). However, it doesn't explicitly differentiate from sibling tools like 'set_tempo' or 'transport' which may overlap in functionality.

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?

Lists supported parameter names which provides implicit scope, but contains no explicit when-to-use guidance, prerequisites, or named alternatives. Doesn't clarify relationship with 'get_project_parameters' or when to use specialized tools like 'transport' versus this generic setter.

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