Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

audio_visual_isolate

Multimodal prompted stem separation into target and residual audio, with a delivery receipt and separate read-only verification of existing payment status (SKU DJ-STEM-001) Unpaid calls return HTTP 402 requirements; retry with payment_signature.

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": {
      "artist_id": "<artist_id>",
      "audio_b64": "<audio_b64>"
    },
    "name": "audio_visual_isolate"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYes
audio_b64Yes
order_refNo
credit_keyNo
visual_boxNo
text_promptNo
wallet_proofNo
output_formatNo
buyer_agent_idNo
temporal_spansNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent mutation, so the write behavior is not new information. The description does add real behavioral context beyond them: a payment gate exists, unpaid calls fail with 402, a delivery receipt is returned, and payment_signature is the retry mechanism. Against that, the 402 sentence is grammatically broken ("return HTTP 402 requirements") and the embedded "read-only verification of payment status" blurs whether this tool reads or writes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

One long run-on sentence that stitches together three or four distinct ideas (separation, receipt, payment status verification, 402 retry) with no structure or front-loading of the primary action. Non-essential material — the SKU and the unrelated read-only verification clause — occupies roughly a third of the text.

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

Completeness2/5

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

This is a complex tool: 12 parameters, 0% schema coverage, no output schema, and a payment/retry protocol. The description explains only the payment failure path and leaves the audio/visual input semantics, the target-versus-residual output contract, and the delivery receipt format undocumented. An agent could not reliably construct a correct call from this definition alone.

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

Parameters2/5

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

Schema description coverage is 0% across 12 parameters, so the description carries the entire burden and it does not meet it. Only payment_signature gets any explanation (the 402 retry path). artist_id, audio_b64, visual_box, temporal_spans, text_prompt, output_format, order_ref, credit_key, wallet_proof, wallet_address, and buyer_agent_id are entirely unexplained, leaving the agent to guess at the multimodal targeting semantics that are the whole point of the tool.

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

Purpose3/5

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

"Multimodal prompted stem separation into target and residual audio" is a specific verb+resource, but the sentence doesn't stop there: it appends a delivery receipt, an SKU, and a "separate read-only verification of existing payment status" that belongs to a different operation (likely audio_payment_status). The core purpose is recoverable but the boundary of what this tool actually does is muddied by packaging a second, unrelated capability into the same definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does give one concrete piece of routing guidance: unpaid calls return HTTP 402 and should be retried with payment_signature. That is genuinely actionable. However, there is no guidance on when to call this versus audio_payment_status (which the description alludes to without naming), nor on which inputs select which mode of "multimodal prompted" separation.

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.

Resources