Skip to main content
Glama

BRAINIAC Crypto Payments

Score invoice payment match

crypto-payments_invoice-match-score

Match caller-supplied payments to invoice amounts, due dates, and fee rates in basis points. Accuracy gives 60 points to the amount, 20 to paying on time, and 20 to the fee. The discrepancy is the invoice total minus the linked payments. No chain is queried. Price $0.04 USDC. POST /api/v1/crypto-payments/invoice-match-score. 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_invoice-match-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoicesYes
paymentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the weighting scheme, the exact discrepancy formula, that no chain RPC occurs, the price, the endpoint, and that unpaid calls return 402 without executing. It omits whether the call is purely computational/idempotent and any rate limits.

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?

Six short sentences, front-loaded with the purpose and scoring model, then operational facts. Every sentence adds a distinct fact and none restates structured data.

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?

No output schema exists, and the description only partially compensates: it explains score composition and the discrepancy definition but not the response shape, the units of integer amounts, or how unmatched invoices and extra payments are handled. For a two-array input with nested items, that leaves meaningful gaps.

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?

Schema coverage is 0%, so the description must compensate. It clarifies that fee rates are in basis points and that payments link to invoices, but the schema's maxItems limits, date format, invoice_id/payment linkage field, and — critically — the integer unit of amounts are left unexplained.

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?

Names a specific verb and resource: matching caller-supplied payments against invoice amount, due date, and fee rates. The scoring breakdown and 'no chain is queried' clause make the operation concrete, though it never names the sibling reconcile tool or explicitly positions itself against it.

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?

'No chain is queried' and 'Match caller-supplied payments' tell the agent this is for offline scoring of data it already holds, which is a real usage signal. It stops short of stating when to prefer the reconcile sibling or what prerequisites (e.g., both arrays non-empty) apply.

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