reaper-mcp

by vecnode

Overview Schema Source Related Servers Discussions Admin

Rust

Local

track_set_color

Set a track's color by specifying red, green, and blue values between 0 and 255.

Instructions

Set a track's color using 0-255 RGB components.

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": {
      "track_index": "<track_index>",
      "r": "<r>",
      "g": "<g>",
      "b": "<b>"
    },
    "name": "track_set_color"
  }
}

Input Schema

Name	Required	Description	Default
`b`	Yes
`g`	Yes
`r`	Yes
`track_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must convey behavioral traits. It correctly indicates that the tool modifies a track's color using RGB values, but does not disclose potential side effects (e.g., persistence, error handling for invalid indices) or return value.

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, efficient sentence that conveys the core purpose without unnecessary words. It is well-structured for quick comprehension.

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?

The tool is simple and the description covers the basic operation, but it lacks information on return values, error conditions, or what happens if the track_index is invalid. Given the absence of an output schema, a bit more detail would improve completeness.

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?

The description adds meaning to three parameters (r, g, b) by specifying the 0-255 range, but does not explain the 'track_index' parameter (e.g., whether it's zero-based). Since schema description coverage is 0%, the description partially compensates but is incomplete.

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 ('Set'), the resource ('track's color'), and the input range ('0-255 RGB components'). This is specific and distinct from sibling tools that deal with other track properties.

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 is provided on when to use this tool versus alternatives, such as when a track exists or what the default color behavior is. The description does not mention prerequisites like track availability or any related constraints.

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