Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_live_open

Idempotent

Switchboard live session allocation: prepaid block of heard minutes per language (default 10, $0.40 per heard language-minute) for /switchboard/live/say phrase synthesis and per-language session recording 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_live_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
credit_keyNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, and the description adds real context beyond that: the pricing model ($0.40 per heard language-minute, default 10), the 402 payment-required error contract with purchase URL/body, and the retry-with-signature semantics. It does not disclose session lifetime or what a successful response returns, but the payment and retry behavior is well covered.

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 purpose is front-loaded and the pricing/error-handling details are relevant, but the text is a single dense run-on with a missing sentence break ('...per-language session recording Pass the exact API body as order') and ambiguous phrasing like 'except credit/topup'. Information earns its place but the structure is muddy.

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 mutating, money-spending tool with a free-form nested body, 0% param coverage and no output schema, the description covers pricing and the 402/payment flow well but omits the shape of the required order object, the success response contents, and what the preserved order_ref/keys are used for. It is adequate for the payment flow but incomplete for correctly constructing the call.

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% across three parameters, so the description carries the burden. It does add meaning for credit_key (spend owned credit, except for credit/topup) and payment_signature (official payment signature), and clarifies order is a raw API body passthrough. But the required free-form nested order object remains opaque — no field shape is given — so it only partially compensates.

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 states a specific verb and resource — allocating a live session with a prepaid block of heard language-minutes — and ties it to /switchboard/live/say synthesis and per-language recording. It is clear what the tool does, though it never explicitly contrasts itself with siblings like switchboard_live_close or switchboard_live_extend, and the dense jargon blurs the core purpose slightly.

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?

It gives genuinely useful conditional guidance for the payment path: an unpaid call returns HTTP 402 with requirements, retry with payment_signature, or use credit_key to spend owned credit. However, it never states when to call this versus alternatives (source_open, broadcast_live, live_close) or what the expected session lifecycle is, so the when-to-use framing is only implied.

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