Skip to main content
Glama
Sign In
Dot RVC Bridge

Dot RVC Bridge

by EllaZhangCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_voice_bypass

Idempotent

Toggle original-voice bypass for the RVC voice-conversion engine on or off. Keeps engine run state and Windows audio routing unchanged.

Instructions

开启原声旁路或关闭旁路使用 RVC；保留引擎启停状态，不改变 Windows 音频路由。

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": {
      "enabled": "<enabled>"
    },
    "name": "set_voice_bypass"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds genuinely non-obvious side-effect context: the engine start/stop state is preserved and Windows audio routing is untouched. That is real behavioral value beyond structured fields.

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

Conciseness4/5

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

A single dense sentence with the action front-loaded and the two constraints (engine state, routing) appended. No filler, though the semicolon-clause structure is slightly packed.

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. Given it is a non-destructive, idempotent toggle whose side effects and state preservation are disclosed, the definition is complete enough for correct invocation.

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 the single boolean is documented only as 'Enabled'. The description compensates by defining the polarity semantically: true = original-voice bypass, false = use RVC. That maps the boolean to real behavior, which the schema alone does not.

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?

States a specific verb+resource ('set voice bypass') and explains the two directions: enabling routes the original voice through, disabling routes through RVC voice conversion. This distinguishes it from the audio/model siblings, though it doesn't name a specific alternative tool.

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 two-state behavior implies when each mode applies, but there is no explicit when-to-use guidance versus siblings like start_voice_audio or select_voice_model, and no prerequisites stated. Usage must be inferred.

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