reaper-mcp

by vecnode

Overview Schema Source Related Servers Discussions Admin

Rust

Local

view_set_arrange_zoom

Set the arrange view's horizontal zoom level in pixels per second. Controls timeline density for detailed editing.

Instructions

Set the arrange view's horizontal zoom level, in pixels per second.

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": {
      "pixels_per_sec": "<pixels_per_sec>"
    },
    "name": "view_set_arrange_zoom"
  }
}

Input Schema

Name	Required	Description	Default
`pixels_per_sec`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided; description carries full burden. Only mentions unit but no side effects, safety, or validation behavior. Lacks disclosure of what happens with invalid values or whether it's a read/write 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?

Single sentence, front-loaded with key action and resource. No redundant words or information. Efficient for quick parsing.

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?

Simple tool with one parameter; no output schema. Description omits return value (perhaps none) and validation behavior. Adequate for basic understanding but leaves gaps for an agent deciding to use it.

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 0%, description adds unit context ('pixels per second') beyond schema's title, but does not specify valid range, constraints, or behavior for the parameter. Baseline 3 due to low coverage and minimal added value.

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?

Clearly states verb 'set', resource 'arrange view's horizontal zoom level', and unit 'pixels per second'. Distinguishes from sibling tools like view_zoom_to_selection and view_scroll_to.

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 on when to use this tool over alternatives like view_zoom_to_selection or zoom via keyboard. Implied usage for explicit zoom level setting, but no exclusions or context.

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