Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_delayed

Idempotent

Switchboard delayed return: up to 8 English sentences translated and synthesized as one program per language with receipt latency telemetry ($0.35 per language) 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_delayed"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
credit_keyNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare write, open-world, idempotent and non-destructive, so the description carries real weight and delivers: per-language cost of $0.35, an 8-sentence cap, the HTTP 402 unpaid flow returning the purchase URL/body, and the credit_key spend path. What it omits is how the delayed result is later retrieved (presumably a job id via a sibling) and whether the call returns immediately, which matters for an async-sounding tool.

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 content is dense and mostly front-loaded, but it reads as a run-on: the price parenthetical runs straight into 'Pass the exact API body as order' with no sentence break, and payment mechanics are interleaved with parameter hints. Little is wasted, but the structure impedes scanning.

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 paid, open-world, likely asynchronous tool with a nested free-form parameter and no output schema, the description covers cost, payment/error flow, and key preservation but never explains the shape of the order body or how the delayed result is collected. It is workable but leaves an agent guessing on the two highest-risk points.

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%, so the description must compensate, and it only partly does: it clarifies credit_key (spends owned credit, except credit/topup) and payment_signature (official payment signature on retry), and hints at order_ref plus read/session keys inside order. Critically, the free-form required 'order' object is described only as 'the exact API body' with no field list, leaving the most important parameter under-specified.

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 first clause states a concrete verb and resource: translate and synthesize up to 8 English sentences into one program per language, with latency telemetry and per-language pricing. That is far more specific than a restated name, though it never contrasts itself with siblings such as switchboard_quote or switchboard_live_say, so the agent must infer when 'delayed' is the right variant.

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

Usage Guidelines2/5

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

The description gives operational routing for payment (retry with payment_signature, or spend owned credit via credit_key except credit/topup), which is useful conditional logic. However, it offers no guidance on when to choose this tool over the live/quote/broadcast alternatives, and no prerequisite context for the caller.

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