Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

set_input_monitoring

Control input monitoring on REAPER tracks to enable, disable, or set conditional monitoring based on playback state.

Instructions

Set input monitoring mode for a track.

  • mode: 0 = off, 1 = on, 2 = not when playing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
modeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:967-977 (handler)
    The MCP tool registration and handler entry point for set_input_monitoring.
    @mcp.tool()
def set_input_monitoring(track_index: int, mode: int) -> dict[str, Any]:
    """
    Set input monitoring mode for a track.
    - mode: 0 = off, 1 = on, 2 = not when playing
    """
    try:
        return _wrap(
            adapter.set_input_monitoring(track_index=track_index, mode=mode)
        )
    except Exception as exc:
  • src/reaper_mcp/reaper_adapter.py:520-528 (handler)
    The adapter method that calls the underlying REAPER client for set_input_monitoring.
    def set_input_monitoring(
    self, track_index: int, mode: int
) -> dict[str, Any]:
    """mode: 0=off, 1=on, 2=not when playing"""
    return self._client.call(
        "set_input_monitoring",
        track_index=track_index,
        mode=mode,
    )

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It documents the three mode states (0=off, 1=on, 2=not when playing), explaining what the system does in each state, but omits other behavioral traits like error handling, persistence across sessions, or side effects on audio processing.

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 efficient lines with zero filler content. The first sentence states purpose; the second uses a clear bullet format to document mode values. Every element earns its place with no redundancy.

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?

Given the tool has only 2 parameters and an output schema exists (per context signals), the description need not explain return values. However, with 0% schema coverage and no annotations, it minimally compensates by documenting only the mode parameter, leaving track_index semantically undefined.

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 description coverage is 0%, requiring the description to compensate. It successfully documents the enum semantics for mode (0, 1, 2 meanings), but provides no clarification for track_index such as whether it is zero-indexed, required track state, or valid ranges.

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 'Set input monitoring mode for a track' provides a specific verb (Set), resource (input monitoring mode), and scope (for a track). It implicitly distinguishes from siblings like set_track_input (which likely configures hardware input) by focusing specifically on monitoring behavior, though it does not explicitly contrast with alternatives.

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?

The description provides no guidance on when to use this tool versus set_track_properties or set_track_input, nor does it mention prerequisites like track existence or project state. It purely states the operation without contextual selectors.

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