reaper-mcp

by vecnode

Overview Schema Source Related Servers Discussions Admin

Rust

Local

view_scroll_to

Scroll the arrange view to a given time position in seconds, making it visible.

Instructions

Scroll the arrange view so the given position (seconds) is visible.

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": "view_scroll_to"
  }
}

Input Schema

Name	Required	Description	Default
`position_sec`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A4/5.0

Behavior3/5

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

The description states that the tool scrolls the view, which is a visual operation. It does not mention side effects, safety, or whether it changes any state. Given no annotations, the description is adequate but could be more transparent about being a read-only view operation.

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?

The description is a single, well-structured sentence that conveys the essential information without redundancy. Every word is necessary.

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?

For a simple tool with one parameter and no output schema, the description covers the core functionality and parameter meaning. It lacks detail on edge cases like out-of-range positions, but this is minor.

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 description adds meaning to the parameter by stating it is a position in seconds, which clarifies the unit. The schema only shows the parameter name and type, so the description provides necessary context.

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 action 'scroll' and the target 'arrange view', and specifies that it scrolls to a given time position in seconds. It is distinct from sibling tools like view_set_arrange_zoom and view_zoom_to_selection, which involve zooming rather than scrolling.

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 use when needing to bring a specific time position into view. However, it does not explicitly state when not to use it or mention alternative tools for similar purposes. Context is clear but lacks exclusion criteria.

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