Skip to main content
Glama

get_project_parameters

Retrieve project playback settings including loop range, cursor position, and loop status for REAPER DAW control.

Instructions

Return loop range, cursor position, and loop-enabled state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_project_parameters'. Calls the adapter's implementation and wraps the result.
    @mcp.tool()
    def get_project_parameters() -> dict[str, Any]:
        """Return loop range, cursor position, and loop-enabled state."""
        try:
            return _wrap(adapter.get_project_parameters())
        except Exception as exc:
            return _err(exc)
  • ReaperAdapter method that calls the bridge client to execute the 'get_project_parameters' request.
    def get_project_parameters(self) -> dict[str, Any]:
        return self._client.call("get_project_parameters")
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It reveals what values are returned, but does not explicitly state that this is a read-only operation, whether values are cached or real-time, or any potential side effects.

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?

At seven words, the description is extremely concise with no redundancy. It front-loads the action verb and immediately specifies the return values, with every sentence earning its place.

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 parameters and an output schema exists (per context signals), the description appropriately focuses on stating what data is retrieved rather than duplicating return value documentation. A slight gap remains in not addressing the relationship to `set_project_parameter`.

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 tool has zero parameters and 100% schema coverage, which establishes a baseline of 4. No additional parameter guidance is needed or provided in the description.

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 a specific verb ("Return") and explicitly names the three resources retrieved (loop range, cursor position, loop-enabled state). However, it does not explicitly differentiate from siblings like `get_project_info` or clarify when to use this versus other getters.

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 versus alternatives like `get_project_info`, nor are there any prerequisites, conditions, or exclusion criteria 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/danielkinahan/ReaMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server