Skip to main content
Glama

Get RVC training requirements

get_training_requirements
Read-only

Use this before training an AI voice to confirm NiceVois input formats, duration and epoch limits, consent requirements, outputs, retention, and the exact upload workflow.

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_training_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
outputsYes
serviceYes
workflowYes
maxEpochsYes
minEpochsYes
agreementUrlYes
consentModelYes
paidTrainingYes
freeAllowanceYes
maxAudioBytesYes
retentionDaysYes
authenticationYes
consentVersionYes
supportedFormatsYes
maxDurationSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / paidTraining / properties / balanceType
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / paidTraining / properties / funding
      Added value: +{
      +  "const": "training_pass_or_subscription",
      +  "type": "string"
      +}
    • addedOutput schema / properties / paidTraining / properties / unit
      Added value: +{
      +  "const": "training",
      +  "type": "string"
      +}
    • changedOutput schema / properties / paidTraining / required
      Previous value: -[
      -  "enabled",
      -  "currency",
      -  "balanceType",
      -  "quoteBeforeUpload",
      -  "maxEpochs",
      -  "maxDurationSeconds",
      -  "accountStatusTool",
      -  "quoteTool"
      -]New value: +[
      +  "enabled",
      +  "currency",
      +  "unit",
      +  "funding",
      +  "quoteBeforeUpload",
      +  "maxEpochs",
      +  "maxDurationSeconds",
      +  "accountStatusTool",
      +  "quoteTool"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / freeAllowance
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "anonymousWebsiteRuns": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "codingAgentOAuthCountsAsConnectedAccount": {
      +      "type": "boolean"
      +    },
      +    "connectedAccountRuns": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxDurationSeconds": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxEpochs": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "anonymousWebsiteRuns",
      +    "connectedAccountRuns",
      +    "maxEpochs",
      +    "maxDurationSeconds",
      +    "codingAgentOAuthCountsAsConnectedAccount"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / paidTraining
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "accountStatusTool": {
      +      "type": "string"
      +    },
      +    "balanceType": {
      +      "type": "string"
      +    },
      +    "currency": {
      +      "type": "string"
      +    },
      +    "enabled": {
      +      "type": "boolean"
      +    },
      +    "maxDurationSeconds": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "maxEpochs": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "quoteBeforeUpload": {
      +      "type": "boolean"
      +    },
      +    "quoteTool": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "enabled",
      +    "currency",
      +    "balanceType",
      +    "quoteBeforeUpload",
      +    "maxEpochs",
      +    "maxDurationSeconds",
      +    "accountStatusTool",
      +    "quoteTool"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "service",
      -  "workflow",
      -  "supportedFormats",
      -  "minEpochs",
      -  "maxEpochs",
      -  "maxDurationSeconds",
      -  "maxAudioBytes",
      -  "outputs",
      -  "retentionDays",
      -  "consentModel",
      -  "consentVersion",
      -  "agreementUrl",
      -  "authentication"
      -]New value: +[
      +  "service",
      +  "workflow",
      +  "supportedFormats",
      +  "minEpochs",
      +  "maxEpochs",
      +  "maxDurationSeconds",
      +  "maxAudioBytes",
      +  "outputs",
      +  "retentionDays",
      +  "consentModel",
      +  "consentVersion",
      +  "agreementUrl",
      +  "authentication",
      +  "freeAllowance",
      +  "paidTraining"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the meaningful behavioral fact that this is a prerequisite step whose content spans limits, consent, and retention — context not derivable from annotations. It does not say whether the content is static documentation or account-dependent, which would have pushed it higher.

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?

A single sentence with the timing cue front-loaded and no filler. Every listed item adds a distinct content category rather than restating the tool name.

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?

With zero parameters and an output schema present, the description need not explain return values, and it correctly focuses on when to call. It is nearly complete; the only gap is not clarifying whether the call is required versus advisory, and not addressing the near-identical conversion-requirements sibling.

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 no parameter meaning to add; baseline 4 applies. The enumerated content areas in the description usefully preview what the parameterless call yields.

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 names a specific resource and enumerates what it returns: NiceVois input formats, duration/epoch limits, consent requirements, outputs, retention, and the upload workflow. An agent can tell this is a pre-flight specification lookup rather than an action tool. It does not explicitly distinguish itself from the sibling get_conversion_requirements, leaving that differentiation implicit in 'training an AI voice'.

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?

It gives an explicit precondition — 'Use this before training an AI voice' — which tells the agent exactly when in the workflow to call it. It stops short of naming alternatives or stating when not to call it (e.g., whether it is mandatory or safe to skip).

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