Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_chunk

Idempotent

Switchboard small chunk: one or two English sentences synthesized in up to 11 target languages (stock voices), returning AAC audio per language and a WAV master ($0.15 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_chunk"
  }
}

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?

Well beyond the annotations: it discloses cost ($0.15 per language), the exact failure mode of an unpaid call (HTTP 402 with requirements and purchase URL/body), and the recovery paths (payment signature or owned credit, with the credit/topup exclusion). It also flags that order_ref and buyer-supplied read/session keys must be preserved. The main gap is that 'up to 11 target languages' is never enumerated, so the agent cannot predict which languages are valid.

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?

Every sentence adds information and the purpose is front-loaded, but the text is a run-on paragraph with missing punctuation ('...($0.15 per language) Pass the exact API body...'), which makes the payment and key-preservation instructions harder to parse than they need to be.

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 a paid, open-world, nested-body tool with no output schema, the description covers cost, authentication, error handling, and key preservation, which is most of what an agent needs. It falls short on the shape and provenance of the order body and on the language set, both of which the schema does not supply either.

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

Parameters4/5

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

With 0% schema coverage this description has to carry all three parameters, and it largely does: order is a passthrough of the exact API body, credit_key spends owned credit (excluding credit/topup), and payment_signature is the official signature used on retry. What it never says is where the API body comes from or what it must contain, leaving the nested free-form object opaque.

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?

States a concrete action and output: synthesize one or two English sentences into up to 11 languages, returning AAC files per language plus a WAV master, with a per-language price. The 'small chunk' framing implicitly contrasts with longer-form siblings, but no sibling is named, so the boundary is only inferable.

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?

Scope ('one or two English sentences') implies when this is the right call versus a longer show or broadcast pack, but no alternative is named explicitly. The strong procedural guidance that exists concerns the payment path (402, payment signature, credit_key), not tool selection.

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