Skip to main content
Glama

set_send_volume

Adjust the volume of a specific audio send in decibels by defining the source track index, send index, and target volume level.

Instructions

Set the volume of a send in dB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_track_indexYes
send_indexYes
volume_dbYes

Implementation Reference

  • The main tool handler for set_send_volume. Converts dB to linear using _db_to_linear helper and sets the send volume via RPR.SetTrackSendInfo_Value.
    @mcp.tool()
    def set_send_volume(source_track_index: int, send_index: int, volume_db: float) -> dict:
        """Set the volume of a send in dB."""
        try:
            project = get_project()
            track = project.tracks[source_track_index]
            RPR.SetTrackSendInfo_Value(track.id, 0, send_index, "D_VOL", _db_to_linear(volume_db))
            return {
                "success": True,
                "source_track_index": source_track_index,
                "send_index": send_index,
                "volume_db": volume_db,
            }
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Registration entry point: mixing_tools.register_tools() is called from server.py, which registers all @mcp.tool() decorated functions including set_send_volume.
    def register_tools(mcp):
  • server.py imports mixing_tools.register_tools and calls it with the mcp instance to register all mixing tools.
    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)
  • Helper function used by set_send_volume to convert decibel values to linear scale for REAPER's API.
    def _db_to_linear(db: float) -> float:
        if db <= -150:
            return 0.0
        return 10 ** (db / 20.0)
  • Helper used by set_send_volume to get the REAPER project connection.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior2/5

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

No annotations provided, so description must carry full burden. It only states the basic operation without disclosing side effects, limits on dB range, immediate vs. queued effect, or whether the send volume is adjusted relative or absolute. Minimal behavioral context.

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?

A single sentence that is efficient and front-loaded. Could be expanded without becoming verbose, but as is it is concise and to the point.

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?

With 3 required parameters, no schema descriptions, no output schema, and no annotations, the description fails to provide enough context for correct invocation. Agent lacks guidance on parameter semantics and expected behavior.

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%. Description adds meaning for volume_db (in dB) but does not explain source_track_index or send_index (e.g., indexing start at 0, how to obtain them). Inadequate compensation for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Set the volume of a send in dB' clearly specifies the action (set), the resource (volume of a send), and the unit (dB). It distinguishes from sibling tools like set_track_volume and create_send.

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 (e.g., set_track_volume, adjust_volume_automation) or prerequisites (e.g., the send must exist). Implied usage from name but no explicit context.

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