Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

Get X402 Account Status

x402_get_account
Read-onlyIdempotent

Read current prepaid USD balance, key role (master vs delegate), emergency freeze status, active delegated subagent keys, pending escalation approvals, and recent spend orders. Use this for live operational status checks and to locate delegate_id (sbd_*) or pending approval_id (sba_*) records; do not use this for double-entry financial reconciliation or date-range exports (use x402_export_statement) or per-call policy preflight (use x402_quote_plan). Free and read-only; requires a valid master or delegated sbk_* spend key (returns HTTP 401 if missing, invalid, or revoked; 120 req/min/IP limit).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
spend_keyNoStripe-funded master or delegated subagent spend key (format: sbk_<43+ chars>). Optional when the caller supplies the x-atlas-spend-key HTTP header.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the account snapshot succeeded.
frozenNoTrue when the emergency freeze kill switch is currently halting all spends.
key_roleNoAuthority tier of the supplied spend key.
account_idNoAccount identifier (format: sbc_<24 hex chars>).
balance_usdNoAvailable prepaid USD balance (e.g. "24.95").
delegates_activeNoCount of non-revoked delegated subagent keys.
pending_approvalsNoCount of pending single-use escalation tickets awaiting operator decision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing the auth model (valid master or delegated sbk_* spend key, HTTP 401 on missing/invalid/revoked key), the rate limit (120 req/min/IP), and that the call is free. These are operational facts an agent cannot get from structured fields and that directly affect retry and error-handling behavior.

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?

The single paragraph is front-loaded with the returned data, then routing guidance, then auth/limits, so an agent gets the highest-value information first. It is dense but nearly every clause earns its place; the enumeration of six returned fields is long, though each item maps to a real capability.

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

Completeness5/5

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

For a read-only status tool with an output schema already defining return values, the description supplies everything else an agent needs: what is returned at a high level, when to call it, what to call instead, auth requirements, failure mode, and rate ceiling. No material gap remains.

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?

There is a single parameter with 100% schema description coverage, including the sbk_ regex pattern and the x-atlas-spend-key header alternative, so the schema carries the semantics. The description restates that a valid master or delegated sbk_* key is required but adds no format, precedence, or header-vs-body guidance beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb (Read) and enumerates exactly what the resource contains: prepaid USD balance, key role master vs delegate, freeze status, delegated subagent keys, pending approvals, recent spend orders. It also names what the tool is not (reconciliation, exports, policy preflight), so an agent can separate it from x402_export_statement and x402_quote_plan without opening schemas.

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

Usage Guidelines5/5

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

Explicitly states the use case (live operational status checks, locating delegate_id sbd_* or approval_id sba_* records) and pairs each exclusion with the sibling that should be used instead: x402_export_statement for date-range exports/reconciliation and x402_quote_plan for per-call policy preflight. Nothing about routing is left to inference.

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