Skip to main content
Glama

create_send

Create an auxiliary send from a source track to a destination track in REAPER, with optional volume adjustment. Streamline routing for mixing and effects processing.

Instructions

Create an aux send from one track to another.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_track_indexYes
dest_track_indexYes
volume_dbNo

Implementation Reference

  • The core handler function for the 'create_send' tool. It takes source_track_index, dest_track_index, and optional volume_db, creates an audio send between two tracks using RPR.CreateTrackSend, and sets the volume with RPR.SetTrackSendInfo_Value.
    def create_send(
        source_track_index: int, dest_track_index: int, volume_db: float = 0.0
    ) -> dict:
        """Create an aux send from one track to another."""
        try:
            project = get_project()
            src = project.tracks[source_track_index]
            dst = project.tracks[dest_track_index]
            send_idx = RPR.CreateTrackSend(src.id, dst.id)
            if send_idx < 0:
                return {"success": False, "error": "Failed to create send"}
            RPR.SetTrackSendInfo_Value(src.id, 0, send_idx, "D_VOL", _db_to_linear(volume_db))
            return {
                "success": True,
                "source_track_index": source_track_index,
                "dest_track_index": dest_track_index,
                "send_index": send_idx,
                "volume_db": volume_db,
            }
        except Exception as e:
            return {"success": False, "error": str(e)}
  • The tool is registered via the @mcp.tool() decorator in the register_tools function inside mixing_tools.py.
    @mcp.tool()
    def create_send(
  • The _db_to_linear helper function converts decibel values to linear scale, used by create_send when setting the send volume.
    def _db_to_linear(db: float) -> float:
        if db <= -150:
            return 0.0
        return 10 ** (db / 20.0)
  • The mixing_tools module (which contains create_send) is imported and its register_tools is called in server.py to register all mixing tools with the MCP server.
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
    from reaper_mcp.render_tools import register_tools as _reg_render
    from reaper_mcp.mastering_tools import register_tools as _reg_mastering
    from reaper_mcp.analysis_tools import register_tools as _reg_analysis
    
    _reg_project(mcp)
    _reg_track(mcp)
    _reg_midi(mcp)
    _reg_fx(mcp)
    _reg_audio(mcp)
    _reg_mixing(mcp)
    _reg_render(mcp)
    _reg_mastering(mcp)
    _reg_analysis(mcp)
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits (e.g., whether it overwrites existing sends, if it requires specific track types, or what happens to the routing). The mutation effect is implied but not detailed.

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?

The description is a single sentence with no extraneous content. While concise, it sacrifices detail that could aid an agent. It is efficiently structured but overly minimal.

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

Completeness2/5

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

Given the tool involves creating a routing connection between tracks, the description lacks details on routing implications, error conditions (e.g., invalid indices), and the return value. It is insufficient for an agent to understand the full impact.

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%, yet the description only mentions 'from one track to another' without explaining the parameters (source_track_index, dest_track_index, volume_db). The meaning of indices, default volume, and optional nature of volume_db are not clarified.

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 states the verb 'create' and the resource 'aux send', with source and destination tracks specified. This distinguishes it from sibling tools like 'create_bus' or 'create_track'. However, 'aux send' might be slightly ambiguous without domain knowledge.

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 on when to use this tool versus alternatives like 'set_send_volume' or 'remove_send'. Missing context on prerequisites, such as whether tracks must already exist or have specific routing.

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/bonfire-audio/reaper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server