Skip to main content
Glama

get_project_info

Retrieve metadata from the currently open REAPER project to access project details and settings within the digital audio workstation.

Instructions

Return metadata about the currently open REAPER project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for get_project_info, which wraps the call to the adapter.
    @mcp.tool()
    def get_project_info() -> dict[str, Any]:
        """Return metadata about the currently open REAPER project."""
        try:
            return _wrap(adapter.get_project_info())
        except Exception as exc:
            return _err(exc)
  • The adapter method that delegates the call to the underlying BridgeClient.
    def get_project_info(self) -> dict[str, Any]:
        return self._client.call("get_project_info")
Behavior3/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. It adds essential behavioral context by specifying 'currently open' project, implying state dependency and temporal scope. However, it omits error behavior (what happens if no project is open), performance characteristics, or specific metadata categories covered.

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 no waste. The information is front-loaded with the action ('Return') followed by the specific resource scope. Every word serves the definition without redundancy.

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?

Given the tool has zero input parameters and an output schema exists (not shown but indicated in context), the description is appropriately scoped. It adequately covers the tool's purpose for a simple getter, though it could benefit from noting error states or specific metadata fields returned.

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. Per the rubric, zero parameters establishes a baseline score of 4. The description appropriately does not invent parameters, maintaining consistency with the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Return') and resource ('metadata about the currently open REAPER project'). It implicitly distinguishes from track/item-level siblings (get_track, get_item_properties) by focusing on project scope, though it doesn't explicitly differentiate from the similar get_project_parameters tool.

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?

The description provides no guidance on when to use this tool versus alternatives like get_project_parameters or prerequisite conditions (e.g., requiring an open project). There are no explicit when/when-not statements.

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