Skip to main content
Glama

set_track_send

Adjust volume and pan settings for track sends in REAPER projects to control audio routing and balance within your mix.

Instructions

Set the volume and/or pan of a track send.

  • volume: linear amplitude (1.0 = 0 dB)

  • pan: -1.0 (full left) to 1.0 (full right)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
send_indexYes
volumeNo
panNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation in the adapter, which forwards the call to the BridgeClient.
    def set_track_send(
        self,
        track_index: int,
        send_index: int,
        volume: float | None = None,
        pan: float | None = None,
    ) -> dict[str, Any]:
        return self._client.call(
            "set_track_send",
            track_index=track_index,
            send_index=send_index,
            volume=volume,
            pan=pan,
        )
  • Tool registration and entry point wrapper.
    def set_track_send(
        track_index: int,
        send_index: int,
        volume: float | None = None,
        pan: float | None = None,
    ) -> dict[str, Any]:
        """
        Set the volume and/or pan of a track send.
        - volume: linear amplitude (1.0 = 0 dB)
        - pan: -1.0 (full left) to 1.0 (full right)
        """
        try:
            return _wrap(
                adapter.set_track_send(
                    track_index=track_index,
                    send_index=send_index,
                    volume=volume,
                    pan=pan,
                )
            )
        except Exception as exc:
            return _err(exc)
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 successfully explains the value ranges and units for volume and pan (linear amplitude, -1.0 to 1.0 range), but fails to mention error behavior, what happens with invalid indices, or what the output schema contains.

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 appropriately brief and front-loaded with the main action. The bullet points efficiently convey parameter semantics without verbosity, though the formatting (markdown bullets in a string) is slightly informal.

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 that this is a 4-parameter mutation tool with an output schema, the description adequately covers the optional parameters' semantics but leaves significant gaps regarding required parameters (track/send indices) and makes no mention of the return value or error conditions despite output schema being present.

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 excellent semantic detail for the optional volume and pan parameters (units, reference values, ranges), but completely omits semantic guidance for the required track_index and send_index parameters (e.g., whether they are 0-indexed).

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 clearly states the specific action (Set), the exact resource (track send), and the specific attributes modified (volume and/or pan), distinguishing it from sibling tools like create_track_send or set_track_properties through precise resource specification.

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 states what the tool does but provides no guidance on when to use it versus alternatives (e.g., when to use this versus creating a new send), nor does it mention prerequisites like the send needing to exist first.

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