Skip to main content
Glama
Sign In
reaper-mcp

reaper-mcp

by vecnode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

transport_seek

Navigate to a specific time position in seconds by moving the edit cursor, enabling precise project control.

Instructions

Move the edit cursor to an absolute position in seconds.

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": {
      "position_sec": "<position_sec>"
    },
    "name": "transport_seek"
  }
}

Input Schema

NameRequiredDescriptionDefault
position_secYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/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 states the action but does not disclose side effects, prerequisites, or limitations (e.g., behavior during playback, required state). This is insufficient for a low-context tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no extra words. However, it could be more informative within that sentence, such as mentioning units or constraints, to earn a higher score.

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?

Given the simple nature of the tool (one parameter, no output schema), the description is minimally adequate but lacks important behavioral details. It does not fully compensate for the absence of annotations and schema coverage.

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

Parameters1/5

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

Schema coverage is 0%, and the description adds no meaning to the parameter 'position_sec' beyond the schema. It fails to explain units, range, or expected format, leaving the agent without necessary detail to correctly invoke the tool.

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 (Move), the resource (edit cursor), and the specific action (to an absolute position in seconds). It effectively distinguishes from sibling tools like transport_play or transport_stop, which have different purposes.

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. It does not mention when not to use it or consider other transport controls, leaving the agent without context for selection.

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