Skip to main content
Glama

add_vocals

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Sing new vocals with your lyrics over an instrumental track (Rao/Suno). Returns an id; poll get_generation.

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>",
      "lyrics": "<lyrics>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "add_vocals"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
styleNo
titleNo
lyricsYes
versionNoRao/Suno version id (list_song_tools.recreate.versions); omit for the default. Sets the price.
vocalGenderNo
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.1/5.0
Behavior4/5

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

Annotations cover openWorldHint, idempotentHint and destructiveHint=false, but the description adds the two most decision-relevant facts not in the annotations: the call consumes credits and requires explicit user confirmation, and the result is async (poll get_generation). It does not describe failure modes or whether credits are consumed on a failed run.

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 tight sentences with no filler, and the cost/confirmation warning is deliberately front-loaded ahead of the purpose statement, which is defensible for a credit-spending tool though it slightly delays the 'what it does' answer.

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 7-parameter async creation tool with no output schema, the definition supplies the cost gate, the confirmation requirement, the return shape (an id) and the polling path. The main remaining gap is undocumented semantics for style/title/vocalGender.

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 43% and the description only clarifies 'lyrics' (the user's own lyrics sung over a track) and implicitly the source-track role of id. It adds nothing for style, title, or vocalGender, which are left undocumented in both schema and description, so it only partially compensates for the coverage gap.

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?

States a specific verb and outcome: sing new vocals over an instrumental track using the user's lyrics, with the underlying provider named. The 'returns an id; poll get_generation' clause pins it as an async-creating tool, which separates it from synchronous siblings like add_instrumental or voice_cover.

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?

Explicitly routes to list_song_tools for pricing and mandates stating the price and getting user confirmation before calling, plus points to get_generation for polling. It does not name when to prefer an alternative creative tool (e.g. voice_cover vs add_vocals), but the preconditions and follow-up are clear.

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.