Skip to main content
Glama

load_project

Load an existing REAPER project (.rpp) by specifying its file path, enabling immediate access to all tracks, routing, and mixing settings.

Instructions

Load a REAPER project (.rpp) from the given file path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYes

Implementation Reference

  • The load_project MCP tool handler function. It checks if the project file exists, opens it via RPR.Main_openProject(), retrieves the project via get_project(), and returns project metadata (name, tempo, time signature, path).
    @mcp.tool()
    def load_project(project_path: str) -> dict:
        """Load a REAPER project (.rpp) from the given file path."""
        try:
            if not os.path.exists(project_path):
                return {"success": False, "error": f"File not found: {project_path}"}
            RPR.Main_openProject(project_path)
            project = get_project()
            return {
                "success": True,
                "name": project.name,
                "tempo": project.bpm,
                "time_signature": f"{project.time_signature[0]}/{project.time_signature[1]}",
                "project_path": project_path,
            }
        except Exception as e:
            logger.error(f"load_project failed: {e}")
            return {"success": False, "error": str(e)}
  • The register_tools function that uses @mcp.tool() decorator to register load_project (and other project tools) with the MCP server.
    def register_tools(mcp):
  • Import of the project_tools registration function into the server.
    from reaper_mcp.project_tools import register_tools as _reg_project
  • Invocation of _reg_project(mcp) to register all project tools including load_project.
    _reg_project(mcp)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not explain whether loading replaces the current project or merges, potential side effects, or error handling (e.g., missing file). The description is too minimal to guide safe invocation.

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, well-structured sentence that conveys the essential action and input. Every word earns its place with no redundancy.

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 has one parameter, no output schema, and no annotations, the description should cover return value, effect on state, and error conditions. It lacks details on whether the loaded project replaces the current one or what the response indicates. This leaves significant gaps for an agent.

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?

The only parameter, 'project_path', is described as 'the given file path', which adds basic context beyond the schema's type string. However, it does not specify format validity (absolute vs. relative) or required file extension, leaving room for ambiguity. Schema coverage is 0%, so description partially compensates.

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 verb 'Load', the resource 'REAPER project (.rpp)', and the input (file path). It distinguishes from siblings like 'create_project' which creates a new project rather than loading an existing one.

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 is provided on when to use this tool vs. alternatives like 'create_project' or 'save_project'. There is no mention of prerequisites (e.g., whether a project must already be open) or constraints on the file path format.

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