Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_long_show

Idempotent

Switchboard long show: asynchronous podcast, chapter, or script synthesis up to 90,000 characters producing AAC, MP3, and WAV master outputs per language ($0.40 per language-minute at 900 chars/min, $1.00 minimum per language; status at /switchboard/jobs/{job_id}) Pass the exact API body as order. An unpaid call returns HTTP 402 requirements and the exact purchase URL/body. Retry with the official payment signature, or use credit_key to spend owned credit (except credit/topup). Preserve order_ref and buyer supplied read/session keys.

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": {
      "order": "<order>"
    },
    "name": "switchboard_long_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
credit_keyNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say non-read-only, idempotent, open-world, non-destructive; the description adds the traits that actually matter: the job is asynchronous, cost is $0.40 per language-minute with a $1.00 per-language minimum at 900 chars/min, and progress is polled at /switchboard/jobs/{job_id}. It also discloses the 402 payment handshake and that credit_key is not valid for credit/topup, and the retry-with-signature advice is consistent with idempotentHint=true.

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?

Purpose, limits, pricing, and polling endpoint are front-loaded in the first sentence, which is the right ordering. The paragraph is dense and slightly run-on, and the pricing parenthetical competes with the payment mechanics for attention, but nearly every clause carries actionable information.

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 an async, paid, open-world job tool with no output schema, the description covers lifecycle entry (order body), cost, and status polling, which is most of what an agent needs. The remaining gap is what the order body must contain and how the finished masters are retrieved, neither of which is stated or routed to a sibling.

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 description coverage is 0% and 'order' is a free-form nested object with additionalProperties, so the description must carry the burden. It does explain that order is the verbatim API body and that payment_signature and credit_key are the two payment paths, which is real added meaning. However, it never enumerates the fields the order body requires, leaving the single most important parameter opaque beyond 'pass the body'.

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?

The opening clause names a concrete verb and resource set: asynchronous synthesis of a podcast, chapter, or script, bounded at 90,000 characters, emitting AAC/MP3/WAV masters per language. That is far more specific than a generic 'synthesize' label. It does not name a sibling it is not (e.g. switchboard_chunk for short/segment work), so differentiation is implied by the length ceiling rather than stated.

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?

The description gives clear operational routing for the payment branch: an unpaid call yields HTTP 402 with requirements plus the exact purchase URL/body, then retry with payment_signature or use credit_key. That is genuine when/how guidance for invocation. It stops short of telling the agent when to prefer this over switchboard_chunk or switchboard_quote, so no alternative-tool exclusions are offered.

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