Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Analyze receivable aging risk

trade-finance_receivable-aging-risk-analyze
Read-onlyIdempotent

Bucket supplied invoice outstanding amounts by days past due from the as-of date. Missing due dates stay unlabeled. Price $0.04 USDC. POST /api/v1/trade-finance/receivable-aging-risk-analyze. An unpaid call returns the x402 payment terms and does not run.

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": "trade-finance_receivable-aging-risk-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
partiesNoparties, array. Optional.
invoicesNoinvoices, array. Optional.
contractsNocontracts, array. Optional.
documentsNodocuments, array. Optional.
worldBankNoworldBank, object. Optional.
assignmentsNoassignments, array. Optional.
discountRatePctNodiscountRatePct, number, from 0 to 100. Optional.
lettersOfCreditNolettersOfCredit, array. Optional.

Output Schema

NameRequiredDescriptionDefault
asOfNoasOf. String.
itemsNoitems. Array.
statusNostatus. String.
bucketsNobuckets. Object.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
invoiceCountNoinvoiceCount. Number.
publicSourcesNopublicSources. Array.
amountInventedNoamountInvented. Boolean.
apiKeyRequiredNoapiKeyRequired. Boolean.
creditDecisionNocreditDecision. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
financingApprovedNofinancingApproved. Boolean.
discrepancyInventedNodiscrepancyInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: the $0.04 USDC charge, the underlying POST route, and that an unpaid invocation returns x402 payment terms without executing. That is real operational context the schema and annotations do not carry.

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?

Four short sentences with the analytical purpose front-loaded, followed by the edge case, the price, the endpoint, and the payment failure mode. No filler or hedging. Slightly clipped phrasing ('Missing due dates stay unlabeled') costs a little clarity but nothing is wasted.

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?

An output schema exists, so return values need not be described, and the payment gate is disclosed. For a 13-parameter, deeply nested tool the description is thin on how inputs combine — notably the bucket boundaries themselves are never stated, and it is unclear whether any of the five content parameters (csv, json, text, file, invoices) is required or how precedence works when several are supplied.

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 100%, but the field descriptions are machine-generated tautologies ('csv, string, length 0 to 200000. Optional.'), so the schema conveys shape, not meaning. The description contributes a little semantics by tying asOf to the reference date and pointing at outstanding amounts and due dates, but it never explains the input-mode choices (csv vs json vs text vs file) or which fields the bucketing actually consumes. Baseline 3 applies.

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?

States a specific verb and resource: bucket invoice outstanding amounts by days past due relative to an as-of date. That is far more precise than the title restated. It does not, however, differentiate itself from siblings such as invoice-financing-readiness or credit-exposure-calculate, so an agent must infer that this is the aging-specific analysis.

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 sibling is named as an alternative. The only conditional statement ('An unpaid call returns the x402 payment terms and does not run') describes a failure mode rather than a selection criterion, so an agent gets no routing help.

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