Skip to main content
Glama
Sign In
reaper-mcp

reaper-mcp

by T-Rzeznik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reaper_set_loop_enabled

Idempotent

Control playback repetition by enabling or disabling looping over the current time selection.

Instructions

Enable or disable looped playback (repeat over the time selection).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "enabled": "<enabled>"
    },
    "name": "reaper_set_loop_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYesTrue to enable looped playback, False to disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds that looped playback is over the time selection, clarifying the scope. No contradictions; it provides useful behavioral context beyond the structured fields.

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?

One sentence, front-loaded with the action and context. Every word earns its place; no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple boolean toggle with complete schema and clear annotations, the description covers all necessary context. No output schema needed; the tool's effect is fully disclosed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single boolean parameter is fully described. The description does not add extra semantic meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the verb 'Enable or disable' and the target resource 'looped playback', and specifies the context 'repeat over the time selection'. It effectively distinguishes this from siblings like reaper_transport_play or reaper_set_time_selection.

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 implies when to use (when toggling looped playback) but provides no guidance on when not to use or alternatives. Given the tool's simplicity, this is adequate but not excellent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools