Skip to main content
Glama

process_song

Idempotent

COSTS CREDITS (see list_song_tools): state the price and get the user's confirmation first. Process an existing song. action "wav" = lossless WAV (subscription, free if already converted; no idempotencyKey needed); "vocals" = vocals + instrumental; "stems" = 4 stems (6 with sixStems); "midi" = MIDI transcription. Poll get_process_result.

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>",
      "action": "<action>"
    },
    "name": "process_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSource song id (songs[].id from get_generation / list_songs / save_upload).
actionYes
sixStemsNostems only: 6 stems instead of 4.
outputFormatNovocals / stems file format.mp3
idempotencyKeyNoRequired for vocals / stems / midi. 8-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

A3.8/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds meaningful context beyond that: the operation costs credits, requires user confirmation, WAV is subscription-gated and free if already converted, and results must be polled via get_process_result. However, it does not clarify async job duration, failure modes, or what happens to prior conversions, so it adds value but is not comprehensive.

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?

Front-loads the credit warning and confirmation requirement, then the purpose, then per-action semantics and the polling step. Dense but nearly every clause carries information; the parenthetical "(see list_song_tools)" and terse phrasing cost a little readability.

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?

There is no output schema, and the description compensates by stating that results come from get_process_result, so the agent knows this is an asynchronous job rather than a direct return. Given five parameters and moderate schema coverage, the definition covers what is needed to invoke correctly; only failure/expiry behavior is left unstated.

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?

With 80% schema coverage the baseline is 3, but the description adds real conditional semantics beyond the schema: it explains that idempotencyKey is not needed for "wav" but is required elsewhere, and clarifies outputFormat/two-variant behavior via "4 stems (6 with sixStems)" and "vocals / stems file format." This is genuine cross-parameter meaning, not repetition.

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?

"Process an existing song" is a somewhat generic verb, but the action breakdown ("wav" = lossless WAV, "vocals" = vocals + instrumental, "stems" = 4 stems, "midi" = MIDI transcription) makes concrete what each invocation produces. An agent can distinguish this from siblings like get_process_result or generate_music, though the generic verb alone would not have been sufficient.

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 confirmation before calling, and tells the agent to poll get_process_result afterward. It does not name a when-not-to-use condition or contrast against alternatives such as add_vocals/add_instrumental, which is why it falls 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.