Skip to main content
Glama

Quote an RVC training job

quote_training
Read-only

Call after inspecting the audio and before creating a job. Returns whether the requested training is covered, its technical limits, available pass/pack/plan offers and a private same-account purchase link if needed. Training is counted in whole trainings, not fractional-dollar amounts.

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": {
      "durationSeconds": "<durationSeconds>",
      "epochs": "<epochs>"
    },
    "name": "quote_training"
  }
}

Input Schema

NameRequiredDescriptionDefault
epochsYes
trainingEngineNorvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training (in selected countries) can use either method; after it, training needs a training pass or an eligible subscription.
durationSecondsYes

Output Schema

NameRequiredDescriptionDefault
epochsYes
canStartYes
currencyYes
accountUrlNo
payableCentsYes
freeRunAppliedYes
shortfallCentsYes
durationSecondsYes
quotedPriceCentsNo
balanceAfterCentsNo
balanceBeforeCentsNo
recommendedProductNo
subscriptionCreditAppliedCentsNo
subscriptionCreditRemainingCentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / trainingEngine / description
      Previous value: -"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training (in most countries) can use either method; after it, training needs a training pass or an eligible subscription."New value: +"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training (in selected countries) can use either method; after it, training needs a training pass or an eligible subscription."
  2. Changed1 schema field changed
    • changedInput schema / properties / trainingEngine / description
      Previous value: -"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training can use either method; after it, training needs a training pass or an eligible subscription."New value: +"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training (in most countries) can use either method; after it, training needs a training pass or an eligible subscription."
  3. Changed1 schema field changed
    • changedInput schema / properties / trainingEngine / description
      Previous value: -"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings and requires a training pass or an eligible subscription."New value: +"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings. An account's one free training can use either method; after it, training needs a training pass or an eligible subscription."
  4. Changed1 schema field changed
    • changedInput schema / properties / trainingEngine / description
      Previous value: -"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings."New value: +"rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings and requires a training pass or an eligible subscription."
  5. Changed1 schema field changed
    • addedInput schema / properties / trainingEngine
      Added value: +{
      +  "description": "rvc (default): Standard RVC, portable .pth and .index. nicevois: NiceVois Training (Seed-VC with a finishing pass), which chooses its own settings.",
      +  "enum": [
      +    "rvc",
      +    "nicevois"
      +  ],
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • addedOutput schema / properties / subscriptionCreditAppliedCents
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / subscriptionCreditRemainingCents
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
  7. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this as a safe, read-only, closed-world operation, lowering the burden. The description adds useful behavior: it reports whether training is covered, exposes technical limits and offers, and may return a private same-account purchase link, plus the billing unit (whole trainings, not fractional dollars). Still, it does not say whether the quote is binding, how long it lasts, or whether calling it has side effects such as reserving quota.

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

Conciseness3/5

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

Two sentences, front-loaded with the call-ordering rule and followed by the return payload, which is efficient. The closing sentence about whole-training billing is relevant but slightly displaced, since it matters more for interpreting offers than for invoking the tool.

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 an output schema present, the description need not detail return values, yet it summarizes them, which helps the agent decide whether to call. For a three-parameter read-only tool, the main remaining gap is the undocumented duration and epoch parameters and any note on quote validity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: trainingEngine is well documented in the schema, but durationSeconds and epochs have no descriptions anywhere. The description adds no parameter-level meaning (units for duration, epoch limits, engine trade-offs), so the gap is not compensated.

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 uses a clear 'quote/preflight check' framing: it is called before creating a job and returns coverage, technical limits, offers, and a purchase link. That distinguishes it from create_training_job without naming it explicitly, so it is clear but not fully differentiated from siblings like get_training_requirements.

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?

'Call after inspecting the audio and before creating a job' gives concrete ordering guidance relative to the sibling workflow. It does not state when to skip the call or name alternatives such as get_training_requirements, leaving some inference to the agent.

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