Skip to main content
Glama
Sign In
Dot RVC Bridge

Dot RVC Bridge

by EllaZhangCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pause_voice_audio

Idempotent

Pause the voice-conversion engine's audio output to silence the voice routed to the virtual line; resume by using bypass and start, or switch output back to headphones.

Instructions

请求暂停引擎音频，会使仍路由到虚拟线的 Dot 无声。恢复原声请使用旁路并启动，或手动改回耳机输出。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pause_voice_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover the safety profile (readOnly=false, idempotent=true, destructive=false), so the bar is lower, and the description still adds a real side-effect disclosure: audio routed to the virtual line is silenced. It does not mention permissions, latency, or state-checking, but the effect on the user's audio is the key behavioral fact and it is present.

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 front-loaded sentence states the action and its effect, followed by the recovery path. No filler, though the packed second clause about bypass/headphone output is slightly dense and could be split for readability.

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 zero-parameter mutation with an output schema present, the description supplies what the schema cannot: the audible consequence and how to revert. It omits any notion of error conditions or whether the pause persists across sessions, but is otherwise adequate.

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 tool takes zero parameters, so there is nothing for the description to disambiguate — baseline 4 applies. The description correctly avoids inventing parameter semantics.

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 (pause the engine audio) and describes the concrete effect — Dots routed to the virtual line go silent. It references sibling tools for the reverse operation, giving useful contrast, though it never explicitly frames itself against start_voice_audio as the direct pair.

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?

Gives guidance for undoing the action ('use bypass and start, or manually switch back to headphone output'), which names alternatives, but provides no guidance on when to choose pause over set_voice_bypass in the first place. Usage is implied rather than stated.

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