Skip to main content
Glama

play_project

Start playback of a REAPER project from the current cursor position. This tool begins audio playback immediately from where the cursor is located.

Instructions

Start project playback from the current cursor position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the play_project tool. Sends REAPER's transport play command (1007) to start playback.
    def play_project() -> dict:
        """Start project playback from the current cursor position."""
        try:
            RPR.Main_OnCommand(1007, 0)  # Transport: Play
            return {"success": True, "message": "Playback started"}
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Registration via @mcp.tool() decorator inside register_tools(mcp). The function play_project is declared as an MCP tool.
    @mcp.tool()
    def play_project() -> dict:
        """Start project playback from the current cursor position."""
        try:
            RPR.Main_OnCommand(1007, 0)  # Transport: Play
            return {"success": True, "message": "Playback started"}
        except Exception as e:
            return {"success": False, "error": str(e)}
  • Helper used by other tools in audio_tools.py (though play_project itself doesn't use it, it's part of the same module's helper infrastructure for REAPER connectivity.
    def get_project() -> reapy.Project:
        ensure_connected()
        return reapy.Project()
Behavior4/5

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

The description accurately conveys a non-destructive playback action, which is sufficient given no annotations. It could mention idempotency (e.g., does nothing if already playing) but is otherwise transparent.

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 a single, focused sentence with no extraneous content, efficiently communicating the essential information.

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

Completeness5/5

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

For a simple, parameterless action, the description fully covers the tool's behavior and purpose. No additional context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, so the description does not need to add parameter details. Baseline 4 applies per rubric.

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 action ('start playback') and the context ('from current cursor position'), distinguishing it from related tools like 'stop_transport' and 'start_recording'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case but provides no explicit guidance on when to use this tool versus alternatives (e.g., when to use play vs record). No exclusions or prerequisites are mentioned.

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