Skip to main content
Glama

set_tempo

Adjust the tempo and time signature in REAPER projects to control playback speed and rhythmic structure for audio production.

Instructions

Set the project tempo (and optionally time signature).

  • bpm: beats per minute

  • time_sig_num / time_sig_denom: e.g. 3, 4 for 3/4 time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmYes
time_sig_numNo
time_sig_denomNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool registration and handler implementation for set_tempo, which calls the ReaperAdapter.set_tempo method.
    def set_tempo(
        bpm: float,
        time_sig_num: int | None = None,
        time_sig_denom: int | None = None,
    ) -> dict[str, Any]:
        """
        Set the project tempo (and optionally time signature).
        - bpm: beats per minute
        - time_sig_num / time_sig_denom: e.g. 3, 4 for 3/4 time
        """
        try:
            return _wrap(
                adapter.set_tempo(
                    bpm=bpm,
                    time_sig_num=time_sig_num,
                    time_sig_denom=time_sig_denom,
                )
            )
        except Exception as exc:
            return _err(exc)
  • The ReaperAdapter method set_tempo which communicates with the bridge client to execute the tempo change in REAPER.
    def set_tempo(
        self,
        bpm: float,
        time_sig_num: int | None = None,
        time_sig_denom: int | None = None,
    ) -> dict[str, Any]:
        return self._client.call(
            "set_tempo",
            bpm=bpm,
            time_sig_num=time_sig_num,
            time_sig_denom=time_sig_denom,
        )
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions 'optionally' indicating optional parameters, but lacks critical behavioral details: valid BPM ranges, transport state requirements, undo implications, or effect on existing audio/MIDI items.

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?

Extremely concise two-sentence structure. Main purpose front-loaded, followed by bullet-style parameter clarification. Zero redundancy.

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?

Parameters are documented and output schema exists (covering return values). However, given no annotations and the destructive/mutating nature of tempo changes, the description lacks behavioral completeness regarding side effects and constraints.

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?

Schema has 0% description coverage. Description compensates by defining 'bpm' as 'beats per minute' and providing clear examples for time signature parameters (e.g., '3/4 time'). However, it omits valid ranges and explicit optionality notes.

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?

Clear specific verb 'Set' plus resource 'project tempo'. The verb distinguishes this from sibling 'get_tempo'. The parenthetical '(and optionally time signature)' clarifies the scope extension.

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 provided on when to use this versus get_tempo, prerequisites (e.g., transport state), or side effects on existing media items.

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