Skip to main content
Glama

Get RVC voice conversion requirements

get_conversion_requirements
Read-only

Use this when a user wants to convert vocals with RVC or compare a normal RVC result with NiceVois cleaned consonants and breaths. Returns the real input formats, model choices, workflow, current free-beta policy, and outputs.

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": "get_conversion_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
outputsYes
pricingYes
serviceYes
workflowYes
modelInputsYes
authenticationYes
wholeSongCoverYes
sourceAudioFormatsYes
transposeSemitonesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / wholeSongCover / properties / agentSupport / const
      Previous value: -"discovery_only"New value: +"rest_and_mcp"
    • changedOutput schema / properties / wholeSongCover / properties / status / const
      Previous value: -"private_preview"New value: +"live"
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description adds that the answer reflects the 'current free-beta policy', signaling time-sensitive content. It does not say the call is parameterless or that results are static/instantaneous, and the output schema already covers the return shape.

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?

Two sentences: the trigger condition first, then an enumerated content list. Front-loaded and free of filler, though the second sentence reads as a comma-separated inventory rather than a tight summary.

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, read-only lookup with an output schema, the description supplies what the agent actually needs: when to call it and what subject matter comes back. Nothing critical is missing, though a pointer to create_voice_conversion as the follow-up action would close the loop.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate beyond the empty schema.

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 resource (RVC voice conversion requirements) and enumerates what the answer contains: input formats, model choices, workflow, free-beta policy, outputs. It implicitly contrasts with the sibling create_voice_conversion (which performs conversion) by being the requirements lookup, but never names that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger: use this when a user wants to convert vocals with RVC or compare a normal RVC result with NiceVois cleaned consonants. That gives a clear when-to-use condition, though it never states exclusions or points to get_training_requirements for the analogous training path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources