Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

Export Reconciled Financial Statement

x402_export_statement
Read-onlyIdempotent

Export a double-entry reconciled enterprise financial statement covering Stripe credit top-ups, capability spends, automatic upstream refunds, delegate attribution, and a tamper-evident SHA-256 checksum (statement_sha256). Use this for accounting audits, reconciliation checks, and per-subagent spend reporting; do not use this for a lightweight live balance or active-key lookup (use x402_get_account). Free and read-only; requires a valid sbk_* spend key (delegated keys receive only rows attributed to their own delegate_id). Subject to 120 req/min/IP rate limiting.

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_export_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoUTC calendar date in ISO-8601 YYYY-MM-DD format (e.g. 2026-11-22).
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.
start_dateNoUTC calendar date in ISO-8601 YYYY-MM-DD format (e.g. 2026-11-22).
delegate_idNoUnique delegated subagent key identifier returned by x402_issue_delegate_key or x402_get_account (format: sbd_<16 hex chars>, e.g. sbd_1122334455667788).

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the reconciled statement was generated.
rowsNoChronological ledger entries with USD amounts, routes, payment identifiers, and delegate attribution.
schemaNoStatement schema identifier (atlas.x402.enterprise_statement.v1).
row_countNoNumber of chronological ledger entries included in rows.
account_idNo
reconciliationNo
statement_sha256NoTamper-evident SHA-256 checksum of the statement payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the auth requirement (valid sbk_* spend key), the delegated-key row-scoping rule (only rows attributed to its own delegate_id), the free/read-only cost model, and a concrete rate limit of 120 req/min/IP. These are operational constraints an agent cannot derive from readOnlyHint/idempotentHint alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense but front-loaded paragraph: purpose first, then usage/exclusion, then auth, scoping, and rate limits. Every clause carries actionable information; the enumeration of statement contents is scope-defining rather than filler.

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 export tool with an output schema already documenting return values, the description supplies everything else an agent needs: triggers, exclusions, credential requirements, delegation scoping, and throttling.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about delegate_id behavior — delegated keys see only their own attributed rows — which changes how an agent should interpret results. It does not add date-range semantics beyond the schema's ISO-8601 pattern.

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?

States a specific verb (export) plus a precisely scoped resource (double-entry reconciled enterprise financial statement) and enumerates what the statement covers, including the SHA-256 checksum field. An agent can distinguish this from any live-balance or key-lookup sibling without opening the schema.

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?

Gives positive triggers (accounting audits, reconciliation checks, per-subagent spend reporting) and an explicit exclusion naming the alternative: "do not use this for a lightweight live balance or active-key lookup (use x402_get_account)." The routing decision is fully specified.

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