Skip to main content
Glama

create_bus

Create a new bus track and route selected tracks to it via sends for group processing.

Instructions

Create a new bus track and route the given tracks to it via sends. track_indices: list of track indices to feed into the bus.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
track_indicesYes

Implementation Reference

  • The create_bus tool handler: creates a new bus track and routes given tracks to it via sends. Uses `project.n_tracks` for the new track index, `project.add_track()` to create it, and `RPR.CreateTrackSend()` to route each source track to the bus.
    @mcp.tool()
    def create_bus(name: str, track_indices: list) -> dict:
        """
        Create a new bus track and route the given tracks to it via sends.
        track_indices: list of track indices to feed into the bus.
        """
        try:
            project = get_project()
            bus_idx = project.n_tracks
            project.add_track(bus_idx, name)
            bus_track = project.tracks[bus_idx]
            sends = []
            for idx in track_indices:
                src = project.tracks[idx]
                send_i = RPR.CreateTrackSend(src.id, bus_track.id)
                sends.append({"track_index": idx, "send_index": send_i})
            return {
                "success": True,
                "bus_index": bus_idx,
                "bus_name": name,
                "sends": sends,
            }
        except Exception as e:
            return {"success": False, "error": str(e)}
  • The `register_tools(mcp)` function that registers all mixing tools (including create_bus) via the `@mcp.tool()` decorator. Called from server.py line 25.
    def register_tools(mcp):
  • Import of mixing_tools.register_tools in the server module, which is called on line 25 to register create_bus.
    from reaper_mcp.mixing_tools import register_tools as _reg_mixing
  • Invocation of mixing_tools.register_tools(mcp), which registers the create_bus tool.
    _reg_mixing(mcp)
  • Helper function `get_project()` used by create_bus to obtain the current REAPER project.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior3/5

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

With no annotations, the description carries burden for behavioral disclosure. It states it creates a bus track and routes tracks via sends, but does not explain side effects like whether existing sends are preserved, or what happens to the original tracks. The behavior is partially transparent but incomplete.

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?

The description is two concise sentences. The first states the purpose, the second defines a key parameter. No redundant information; every word adds value.

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?

The description covers the basic action but lacks context about preconditions (tracks must exist), what a bus track is, and what the tool returns. Without an output schema, the return value is not addressed. For a DAW context, the concept is moderately clear but could be more complete.

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?

Only one of two parameters (track_indices) is explained in the description as 'list of track indices to feed into the bus'. The name parameter is not described. With schema coverage at 0%, the description should explain both parameters, but it only covers one.

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 tool creates a new bus track and routes given tracks to it via sends, using specific verb-resource combination. It distinguishes from siblings like create_track (just creates a track) and create_send (creates a send without a bus).

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, such as when to use create_bus vs create_track plus create_send. No mention of prerequisites (e.g., tracks must exist) or conditions like when a bus is needed.

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