Skip to main content
Glama

new_project

Create a new blank REAPER project for audio production and editing within the digital audio workstation.

Instructions

Create a new blank REAPER project (equivalent to File > New Project).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function 'new_project' in 'server.py' which calls 'adapter.new_project()'.
    def new_project() -> dict[str, Any]:
        """Create a new blank REAPER project (equivalent to File > New Project)."""
        try:
            return _wrap(adapter.new_project())
        except Exception as exc:
            return _err(exc)
  • The adapter method 'new_project' in 'reaper_adapter.py' which forwards the request to the underlying BridgeClient.
    def new_project(self) -> dict[str, Any]:
        return self._client.call("new_project")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies mutation, the description fails to disclose critical side effects: whether the current project is closed, whether unsaved changes are discarded or prompted, or what the output schema contains. This omission is significant for a project-switching operation.

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 optimally concise with two efficient fragments: the core action statement and the helpful parenthetical analogy. Every element earns its place without redundancy or wasted words, presenting information in a front-loaded manner.

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 the existence of an output schema, the description appropriately omits return value details. However, for a project lifecycle tool with no annotations, the description minimally suffices by stating the action but omits important lifecycle context (project switching behavior, unsaved change handling) that would make it complete.

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?

The input schema contains zero parameters (empty object), which per the rubric establishes a baseline of 4. The description appropriately does not attempt to invent parameter semantics where none exist, satisfying the requirement for this dimension.

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 provides a specific verb ('Create') and resource ('REAPER project'), with the adjective 'blank' clearly distinguishing it from sibling tool open_project. The parenthetical '(equivalent to File > New Project)' adds valuable context for users familiar with the application's menu structure.

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 offers implied usage guidance through the File > New Project analogy, but lacks explicit when-to-use guidance or contrasts with alternatives like open_project. It does not mention prerequisites (e.g., handling unsaved changes in the current project) despite being a project lifecycle operation.

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