Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_live_extend

Idempotent

Switchboard live session extension: additional prepaid heard minutes for an active live session ($0.40 per language-minute) 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_extend"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
credit_keyNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the per-minute cost, the 402 payment-required response shape (requirements plus exact purchase URL/body), the retry path, and the constraint that credit_key cannot be used for credit/topup. Annotations already cover mutation/openWorld/idempotency, so this is a solid supplement. It still leaves unstated whether purchased minutes expire, whether the extension can fail after payment, and how retries are deduplicated.

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?

Front-loaded with the resource and price, then flows into payment mechanics, with no filler sentences. Some clauses are telegraphic and ambiguous ('except credit/topup', 'buyer supplied read/session keys'), which costs a little readability.

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 mutation with no output schema, the definition covers the money and error path well. It does not describe the success outcome (minutes credited, session validity change) or the contents of the required order body, leaving the highest-risk part of the call undocumented.

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?

With 0% schema coverage, the description is the only documentation: 'order' is clarified as an opaque passthrough API body, and credit_key and payment_signature each get a usage rule. However, the required, nested, free-form 'order' object — the parameter most likely to be misconstructed — has no field-level guidance whatsoever, so the agent must obtain its shape elsewhere.

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 specific verb and resource ('live session extension: additional prepaid heard minutes for an active live session') and even quantifies the unit price at $0.40 per language-minute. It is distinguishable from switchboard_live_open/close/feed by scope, though it never names a sibling to contrast with explicitly.

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?

Gives clear procedural context: call to add minutes to an already-active session, pass the exact API body as order, and on a 402 either retry with the official payment signature or spend owned credit via credit_key. It does not state when to prefer credit over payment, or point to any alternative tool for prepaying before a session opens.

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