Skip to main content
Glama
danielkinahan

ReaMCP

by danielkinahan
OverviewSchemaRelated ServersScoreDiscussions
Local

get_tempo

Retrieve the current BPM and time signature from REAPER projects to synchronize audio editing and playback settings.

Instructions

Return the current BPM and time signature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/reaper_mcp/server.py:608-614 (handler)
    The MCP tool handler for "get_tempo", which wraps the adapter call.
    @mcp.tool()
def get_tempo() -> dict[str, Any]:
    """Return the current BPM and time signature."""
    try:
        return _wrap(adapter.get_tempo())
    except Exception as exc:
        return _err(exc)
  • src/reaper_mcp/reaper_adapter.py:356-357 (handler)
    The adapter method that sends the "get_tempo" command to the bridge client.
    def get_tempo(self) -> dict[str, Any]:
    return self._client.call("get_tempo")

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. 'Return' implies read-only/idempotent behavior but lacks explicit safety confirmation or details about data freshness (cached vs real-time). Output schema existence excuses detailed return value description.

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 of seven words with zero redundancy. High information density: verb (Return), scope (current), and dual return values (BPM, time signature) packed efficiently.

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 simple getter with existing output schema. Mentions the two key return values. Could strengthen by noting relationship to 'set_tempo' or project tempo changes, but sufficient for invocation.

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 rules, baseline score of 4 applies. Description wisely avoids inventing parameter details when schema confirms none exist.

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?

Clear verb ('Return') and specific resources ('current BPM and time signature'). Implicitly distinguishes from sibling 'set_tempo' by using 'Return' vs implied mutation, though explicit contrast with 'get_project_parameters' or 'transport' is absent.

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?

No explicit when-to-use or alternatives named (e.g., when to use vs 'get_project_parameters'). However, usage is implied by the zero-parameter design and 'current' keyword indicating a state snapshot query.

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