Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

create_track_send

Create audio sends between tracks in REAPER to route signals for mixing, effects processing, or parallel processing workflows.

Instructions

Create a send from one track to another. Returns the new send index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
src_track_indexYes
dst_track_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:872-882 (handler)
    The MCP tool registration and handler wrapper for `create_track_send`. It uses `ReaperAdapter` to call the backend.
    @mcp.tool()
def create_track_send(src_track_index: int, dst_track_index: int) -> dict[str, Any]:
    """Create a send from one track to another. Returns the new send index."""
    try:
        return _wrap(
            adapter.create_track_send(
                src_track_index=src_track_index, dst_track_index=dst_track_index
            )
        )
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:474-481 (helper)
    The `ReaperAdapter` implementation of `create_track_send`, which delegates the call to the `BridgeClient`.
    def create_track_send(
    self, src_track_index: int, dst_track_index: int
) -> dict[str, Any]:
    return self._client.call(
        "create_track_send",
        src_track_index=src_track_index,
        dst_track_index=dst_track_index,
    )

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the full burden. It discloses the mutation ('Create') and the return value ('new send index'), but omits error handling behavior, side effects on audio routing, and whether this operation is idempotent or reversible.

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: the first states the operation, the second states the return value. Every word earns its place and the core action is front-loaded.

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 0% schema coverage and lack of annotations, the description covers the essential operation and return value (sufficient since output schema exists), but omits domain-specific context that would aid an agent, such as explaining what 'sends' are used for in audio production or collision behaviors if a send already exists.

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?

With 0% schema description coverage, the description partially compensates by mapping the directional relationship ('from one track to another') to the src/dst parameters, though it does not explicitly document each parameter's role or constraints (e.g., valid index 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 clearly identifies the verb ('Create'), resource ('send'), and scope ('from one track to another'). It distinguishes this from siblings like 'remove_track_send' and 'set_track_send' by specifying this creates a new send and returns its index.

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 explicit guidance on when to use this versus 'set_track_send' (which might update existing sends), nor does it mention prerequisite conditions such as the requirement for both tracks to exist beforehand.

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