Skip to main content
Glama

restyle_song

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Fixed price. Re-arrange a song in a new music style keeping its vocals; pass newLyrics to also re-sing it with new words. Returns an id; poll get_generation (takes a few minutes).

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>",
      "style": "<style>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "restyle_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
styleYesTarget style, e.g. "acoustic folk, fingerpicked guitar".
titleNo
newLyricsNoOptional: new lyrics to re-sing.
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.5/5.0
Behavior5/5

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

Annotations only declare openWorldHint/idempotentHint/destructiveHint; the description adds substantial behavior beyond them: it costs credits at a fixed price, requires explicit user confirmation, returns an id, and is asynchronous with a multi-minute duration. That is exactly the operational context an agent needs before invoking a paid mutation.

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?

Sentences are dense and front-loaded: the cost/confirmation warning comes first, then purpose, then the return/polling contract. There is no filler, and each clause contributes a distinct fact.

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?

With no output schema, the description supplies the return contract (an id) and the polling path (get_generation, a few minutes), plus the credit cost and retention-of-vocals semantics. Nothing critical for correct invocation is missing for a credit-consuming async tool.

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 description adds meaning mainly for newLyrics (re-singing with new words) and implies style behavior, while idempotencyKey and id are already richly documented in the schema. The optional title and vocalGender parameters get no elaboration in the description, leaving the added value modest.

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-arrange a song in a new music style keeping its vocals') and distinguishes variants via 'pass newLyrics to also re-sing it with new words'. An agent can tell this apart from siblings like mashup_songs or voice_cover without opening schemas.

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 key precondition ('state the price and get the user's confirmation first', with a pointer to list_song_tools) and names the follow-up flow (poll get_generation, takes a few minutes). It gives clear context but no explicit when-not or named alternative for style manipulation versus other tools.

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.