Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_media

Idempotent

Switchboard uploaded media dubbing: asynchronous per-language program synthesis from a completed /switchboard/sources upload (source_id and upload_key), priced from measured media duration with 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_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
credit_keyNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, idempotent and non-destructive, but the description adds real behavior: the operation is asynchronous, cost is derived from measured media duration, the unpaid path returns HTTP 402 with exact purchase requirements, and order_ref plus buyer-supplied read/session keys must be preserved. The only soft spot is the cryptic 'except credit/topup' carve-out, which is not explained.

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

Conciseness3/5

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

The payment and prerequisite information is front-loaded well, but the text is a run-on with a missing sentence break ('.../switchboard/jobs/{job_id} Pass the exact API body as order') and the trailing 'Preserve order_ref and buyer supplied read/session keys' is tacked on without context.

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

Completeness3/5

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

For a complex, paid, asynchronous mutation with a free-form nested order object and no output schema, the description covers the payment lifecycle but leaves the shape of order and the identity of the returned job_id/order_ref implicit. An agent could still invoke it, but would likely need to guess at the order payload.

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 0%, so the description carries the burden. It does explain credit_key (spend owned credit, except credit/topup) and payment_signature (official payment signature on retry), but the dominant parameter, order, is only described as 'the exact API body' with no field-level detail despite being a free-form nested object.

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 description uses a specific verb and resource: asynchronous per-language dubbing/program synthesis from a completed /switchboard/sources upload, priced by measured media duration. It is clearly distinct from siblings like switchboard_job_get or switchboard_source_append, though it never names an alternative to contrast against.

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 prerequisite (a completed sources upload with source_id and upload_key) and lays out the payment decision tree: an unpaid call returns HTTP 402 with the purchase URL/body, then retry with the official payment signature or use credit_key. What's missing is guidance on when to pick this over sibling tools such as switchboard_quote or switchboard_chunk.

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