headrush-mcp

Overview Schema Source Related Servers Discussions Admin

set_mix

DestructiveIdempotent

Adjust parallel path levels, pan, delay, and crossfade without saving, using normalized values or display units such as dB, percent, and microseconds.

Instructions

Set parallel path mixing without saving.

Keys: Para1Level, Para2Level, Para1Pan, Para2Pan, ParaDelay, ParaXFade. Values are normalized 0-1: for pans 0 is left, 0.5 centre and 1 right; for level 0.75 is -6 dB. With display, give dB, percent (-100 is left) and microseconds instead.

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": {
      "values": "<values>"
    },
    "name": "set_mix"
  }
}

Input Schema

Name	Required	Description	Default
`values`	Yes
`display`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=true, openWorldHint=false, so the safety profile is covered. The description adds the important behavioral fact that the write is not persisted ('without saving'), which tells the agent the change is reversible/ephemeral until a save occurs. It stops short of saying whether unspecified keys retain their current values or that a rig must be loaded.

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?

Two tight sentences: scope first, then the key list, then unit semantics, with the 'display' alternative last. No filler, and the most decision-relevant fact (no saving) is front-loaded.

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?

An output schema exists, so return values need not be described, and the annotations cover safety. What remains missing is preconditions (must a rig be loaded?) and merge-vs-replace behavior for the values map. For a two-parameter tool with a well-documented key vocabulary, this is close to complete.

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?

Schema coverage is 0% and 'values' is a bare additionalProperties:number object, so the description carries the full burden — and it delivers by enumerating the six valid keys (Para1Level, Para2Level, Para1Pan, Para2Pan, ParaDelay, ParaXFade) and their value conventions. It does not clarify whether partial key sets are allowed or what happens to omitted keys, leaving a real gap for a free-form map parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Set parallel path mixing without saving.' An agent immediately knows this mutates the parallel-path mix and that the change is transient. It does not name which sibling persists the change (save_loaded_rig) or how it differs from set_block_params, so it stops short of explicit sibling differentiation.

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?

Usage is only implied: 'without saving' hints that a save step is required afterward, and the 'display' sentence indicates when to pass human-readable units instead of normalized values. There is no explicit when-to-use / when-not-to-use statement or named alternative tool.

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