Skip to main content
Glama

voice_cover

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Priced per minute of the source. Re-sing a song with another voice (list_voices), keeping the music. Returns an id; poll get_process_result with action "voice_cover".

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": {
      "id": "<id>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "voice_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
voiceNoBuilt-in voice id from list_voices.builtIn.
pitchShiftNono-change
outputFormatNomp3
voiceModelIdNoOr one of the user's own voices from list_voices.custom.
idempotencyKeyYes8-64 chars [A-Za-z0-9._:-]. Same rules as generate_music: stable per logical request, resend the same key + params after a timeout instead of paying twice; new key when anything changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which only cover openWorldHint, idempotentHint, and destructiveHint=false), the description discloses the credit cost model ('Priced per minute of the source'), the mandatory confirmation gate, and the asynchronous return contract ('Returns an id; poll get_process_result...'). These are exactly the behavioral facts an agent needs and none are in the 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.

Conciseness5/5

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

Front-loaded with the highest-risk fact (COSTS CREDITS) and the confirmation requirement, then purpose, then billing, then the return/poll contract. Four compact sentences, zero filler, and the ordering matches the order the agent must reason about them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an async, credit-consuming mutation with no output schema, the description covers cost, consent, the input dependency (source song id), the voice source, and how to retrieve the result. Nothing an agent needs to invoke it safely and correctly is absent.

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

Parameters3/5

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

Schema coverage is 67%, and the schema itself already documents id, voice, voiceModelId, and idempotencyKey thoroughly. The description only reinforces the voice-source routing (list_voices) and hints that the source duration drives price. It adds nothing for pitchShift, outputFormat, or the enum values, so it stays at the baseline for a partially documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource — 'Re-sing a song with another voice ... keeping the music' — which unambiguously separates it from siblings like add_vocals, add_instrumental, or restyle_song. An agent knows exactly what transformation is applied and what is preserved.

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 states the prerequisite sequence explicitly: check price via list_song_tools, state the price, get user confirmation, then call. It also names the follow-up (poll get_process_result with action 'voice_cover') and the voice source (list_voices). It stops short of explicit when-not-to-use guidance against add_vocals-style alternatives, but the 'keeping the music' clause does most of that work implicitly.

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.