Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

set_track_input

Configure recording input sources for tracks in REAPER, specifying audio channel indexes or MIDI device encodings to route signals appropriately.

Instructions

Set the recording input for a track.

  • For audio: 0-based audio input channel index.

  • For MIDI: use REAPER's I_RECINPUT encoding (e.g. 4096 + channel*32 + device).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
input_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:952-964 (handler)
    The MCP tool handler for 'set_track_input', which registers the tool and calls the reaper adapter.
    @mcp.tool()
def set_track_input(track_index: int, input_index: int) -> dict[str, Any]:
    """
    Set the recording input for a track.
    - For audio: 0-based audio input channel index.
    - For MIDI: use REAPER's I_RECINPUT encoding (e.g. 4096 + channel*32 + device).
    """
    try:
        return _wrap(
            adapter.set_track_input(track_index=track_index, input_index=input_index)
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/server.py:952-964 (handler)
    MCP tool handler registration for set_track_input.
    @mcp.tool()
def set_track_input(track_index: int, input_index: int) -> dict[str, Any]:
    """
    Set the recording input for a track.
    - For audio: 0-based audio input channel index.
    - For MIDI: use REAPER's I_RECINPUT encoding (e.g. 4096 + channel*32 + device).
    """
    try:
        return _wrap(
            adapter.set_track_input(track_index=track_index, input_index=input_index)
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:511-518 (helper)
    The adapter method that communicates with the REAPER client to perform the set_track_input action.
    def set_track_input(
    self, track_index: int, input_index: int
) -> dict[str, Any]:
    return self._client.call(
        "set_track_input",
        track_index=track_index,
        input_index=input_index,
    )
  • src/reaper_mcp/reaper_adapter.py:511-518 (helper)
    ReaperAdapter helper method that calls the bridge client for set_track_input.
    def set_track_input(
    self, track_index: int, input_index: int
) -> dict[str, Any]:
    return self._client.call(
        "set_track_input",
        track_index=track_index,
        input_index=input_index,
    )

Tool Definition Quality

B3.2/5.0
Behavior3/5

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

Without annotations, the description carries the full burden. It successfully documents the value encoding scheme (0-based for audio, REAPER I_RECINPUT formula for MIDI), which is critical behavioral context. However, it omits safety details like error handling when indices are out of range.

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?

Three sentences with efficient bullet-point formatting. The core purpose is front-loaded in the first sentence, and the technical details follow without redundancy. No wasted words.

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?

While the encoding explanation provides necessary domain-specific context and an output schema exists (removing the need to describe returns), the description is incomplete due to the missing track_index documentation and lack of guidance on valid ranges or error conditions.

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 provides substantial semantic detail for input_index (explaining the audio vs MIDI encoding schemes), but fails to document track_index at all, leaving one parameter completely undefined.

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 ('Set') on a specific resource ('recording input') for a clear target ('track'). It distinguishes the intent from siblings like set_input_monitoring (which handles monitoring, not recording source), though it doesn't explicitly name 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?

No explicit guidance on when to use this tool versus alternatives (e.g., set_track_properties), nor any prerequisites mentioned (e.g., that the track must exist). Agents must infer usage from the command name alone.

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