Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

save_project

Save the current REAPER project to disk using the ReaMCP server. This tool preserves your audio workstation session by writing project data to storage.

Instructions

Save the current REAPER project to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:657-663 (handler)
    The MCP tool handler for 'save_project', decorated with @mcp.tool(). It calls the adapter method and handles potential exceptions.
    @mcp.tool()
def save_project() -> dict[str, Any]:
    """Save the current REAPER project to disk."""
    try:
        return _wrap(adapter.save_project())
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:382-383 (helper)
    The adapter method that sends the 'save_project' call to the REAPER client.
    def save_project(self) -> dict[str, Any]:
    return self._client.call("save_project")

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. 'To disk' indicates persistent I/O and mutation, but lacks critical behavioral details: failure modes if project is unsaved, whether it performs 'Save' or 'Save As' semantics, and return value structure despite output schema existing.

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?

Single sentence with zero waste. Verb-fronted ('Save') with clear direct object and prepositional phrase. Optimal length for the operation's simplicity.

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

Completeness4/5

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

Adequate for a zero-parameter state-mutation tool where output schema exists (covering return documentation). Could benefit from noting filename/path handling behavior, but sufficient given the straightforward nature of the operation.

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?

Zero parameters present. Per rubric, 0 params = baseline 4. Description appropriately omits parameter discussion as none exist to document.

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?

Specific verb (Save) + specific resource (current REAPER project) + scope (to disk). Implicitly distinguishes from siblings like `new_project` (creates), `open_project` (opens files), and `get_project_info` (reads metadata) by emphasizing the 'current' project and persistence action.

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?

Provides no explicit guidance on when to use versus alternatives (`new_project`, `open_project`) or prerequisites (e.g., requiring an open project). Simply states what the tool does without contextual selection criteria.

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