Skip to main content
Glama

add_instrumental

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Generate backing music for a vocal / a cappella track (Rao/Suno). style is required unless the source already has one. 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>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "add_instrumental"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
styleNo
titleNo
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.7/5.0
Behavior5/5

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

Annotations cover safety (destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds the traits annotations cannot express: the call costs credits, requires user confirmation of price, runs asynchronously, and returns an id that must be polled via get_generation. Nothing contradicts the annotation profile.

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?

Four dense sentences with zero filler, and the highest-stakes information (COSTS CREDITS, confirm first) is front-loaded before any mechanics. Every sentence carries an actionable instruction.

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 supplies everything an agent needs: cost gate, confirmation step, conditional style requirement, the returned id, and the polling tool. No meaningful gap remains.

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?

Schema coverage is only 50%, but the description compensates with a genuinely non-obvious rule: 'style is required unless the source already has one', which the schema does not encode (style is not in required). It also ties cost to the version parameter indirectly via the credits/price warning. title and vocalGender remain self-evident and undescribed, so not a 5.

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 resource: 'Generate backing music for a vocal / a cappella track (Rao/Suno)'. This clearly separates it from sibling operations like add_vocals (the inverse direction), voice_cover, or generate_music without requiring the agent to open any schema.

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?

Gives clear when-to-use context (a vocal/a cappella source needing backing music) plus a prerequisite workflow: check the price via list_song_tools, state it, and get confirmation first. It also names the follow-up path (poll get_generation) but never states an explicit when-not or names a sibling to avoid, which keeps it short of a 5.

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.