Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_statement

Read-onlyIdempotent

Export a double-entry reconciled enterprise financial statement (JSON with SHA-256 reconciliation checksum) covering Stripe top-ups, capability spends, automatic refunds, and delegate attribution.

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": "payment_assistant_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
spend_keyNo
credit_keyNo
start_dateNo
delegate_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that: the output is JSON with a SHA-256 reconciliation checksum, it is double-entry reconciled, and it spans specific transaction categories. It does not disclose what happens when filters are omitted or whether output size/pagination is bounded, which keeps it below a 5.

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?

A single sentence with the verb and output format front-loaded and no filler text. It is jargon-dense ('double-entry reconciled enterprise financial statement') but every clause carries information about output content or format.

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 read-only export tool the description adequately conveys the shape and trust properties of the result, and annotations cover safety. However, with five undocumented optional parameters, no output schema, and no statement of default scope, an agent cannot confidently predict what it will get back or how to narrow the export.

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

Parameters2/5

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

Schema description coverage is 0% and none of the five parameters (start_date, end_date, spend_key, credit_key, delegate_id) are explained. The phrase 'delegate attribution' and the mention of 'capability spends' hint loosely at delegate_id/spend_key, but the literal meaning, pairing rules, and default behavior when all are omitted are left entirely to inference. With zero schema coverage this is a substantial gap.

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 description gives a specific verb ('Export') and a well-defined resource ('double-entry reconciled enterprise financial statement'), plus the data domains it covers (Stripe top-ups, capability spends, refunds, delegate attribution). This clearly separates it from sibling tools like payment_assistant_account or payment_assistant_checkout. It stops short of naming an explicit boundary case or alternative export tool.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of prerequisites such as required permissions or whether a reconciliation window must already be closed. An agent learns what the tool returns but not the conditions under which it should be preferred over manual inspection of account or checkout data.

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