Skip to main content
Glama

BRAINIAC Crypto Payments

Reconcile stablecoin payment

crypto-payments_stablecoin-payment-reconcile

Reconcile caller-supplied stablecoin payment records against invoices. Compares amounts, token, recipient, and chain ID, and reports underpayments, overpayments, duplicate transaction hashes, and payments that are not linked to an invoice. reconciliation_status is matched, underpaid, overpaid, duplicate, mismatched, or incomplete. Amounts are integers in smallest units. No chain is queried, and a transaction hash is not treated as confirmation that funds arrived. Price $0.05 USDC. POST /api/v1/crypto-payments/stablecoin-payment-reconcile. Unpaid calls return 402 and do not run.

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": {
      "invoices": "<invoices>",
      "payments": "<payments>"
    },
    "name": "crypto-payments_stablecoin-payment-reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesNo
invoicesYes
paymentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does it well: it discloses that the operation is a pure comparison over supplied data with no chain access, enumerates the possible reconciliation_status values, specifies the price ($0.05 USDC), names the endpoint, and states that unpaid calls return 402 and do not run. These are exactly the operational facts an agent needs that structured fields do not provide.

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?

Dense and front-loaded, leading with the verb and resource before output categories, units, safety caveat, and billing/transport facts. The trailing mix of price, endpoint, and 402 behavior reads as a terse fact list rather than prose, but nearly every clause earns its place.

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 tool with nested objects, two required arrays, and no output schema, the description covers purpose, reported outcomes, unit conventions, cost, and payment-failure behavior adequately. The remaining gap is the undocumented `rules` sub-object and the absence of any description of the per-record result shape, which an agent would have to infer.

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%, so the description must compensate, and it only partly does: it maps the compared fields (amount, token, recipient, chain ID) to the invoice/payment objects. The entire optional `rules` object — tolerance, allowPartial, associateUnlabeledPayments — is never mentioned, and 'Amounts are integers in smallest units' is ambiguous against a schema whose amount is a string paired with a separate decimals integer, leaving scaling behavior unclear.

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 and resource — reconcile caller-supplied stablecoin payment records against invoices — and its output scope (underpayments, overpayments, duplicates, unlinked payments). The scope qualifiers 'caller-supplied' and 'No chain is queried' separate it from any on-chain verification or scoring sibling.

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 context for when the tool applies and, importantly, a boundary condition: it does not query a chain and does not treat a transaction hash as proof of funds, so an agent knows this is bookkeeping reconciliation rather than settlement verification. It stops short of explicitly naming when to defer to a sibling like invoice-match-score.

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