Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Build trade finance evidence package

trade-finance_evidence-package
Read-onlyIdempotent

Assemble document match, LC discrepancy, readiness, aging, assignment, party, term, exposure, and discounting summaries from the supplied set. Price $0.08 USDC. POST /api/v1/trade-finance/evidence-package. 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_evidence-package"
  }
}

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
itemsNoitems. Array.
statusNostatus. String.
lcCountNolcCount. Number.
findingsNofindings. Array.
sectionsNosections. Object.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
invoiceCountNoinvoiceCount. Number.
contractCountNocontractCount. Number.
documentCountNodocumentCount. Number.
publicSourcesNopublicSources. Array.
amountInventedNoamountInvented. Boolean.
apiKeyRequiredNoapiKeyRequired. Boolean.
creditDecisionNocreditDecision. Boolean.
assignmentCountNoassignmentCount. Number.
paidProviderUsedNopaidProviderUsed. Boolean.
financingApprovedNofinancingApproved. Boolean.
discrepancyInventedNodiscrepancyInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavior they cannot express: a concrete price ($0.08 USDC), the transport endpoint, and critically that an unpaid call returns x402 payment terms and does not execute. That payment failure mode is exactly the kind of operational context an agent needs before calling a metered endpoint.

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?

Three short sentences in a deliberate order: what it produces, what it costs, and how the call fails. No filler, and the capability statement is front-loaded before pricing details.

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?

An output schema exists, so return values need no explanation, and pricing plus payment semantics are covered. The one remaining gap is whether all nine summary sections are always returned or only those for which input data was supplied — useful given that every top-level parameter is optional.

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 description coverage is 100%, so every one of the 13 parameters (including nested invoice, LC, document, contract, assignment and party objects) is already documented structurally. The description adds only the vague hint that inputs come 'from the supplied set' and gives no guidance on which of csv/json/text/file to use or how asOf and discountRatePct affect the output.

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 ('Assemble') and resource ('evidence package') and enumerates the nine summary types it produces, which map one-to-one onto the sibling analysis tools. An agent can immediately see this is the aggregate roll-up rather than a single analysis.

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?

The phrase 'from the supplied set' and the enumeration of all component summaries make the aggregation use case clear, implying this is the one-call alternative to invoking the nine siblings individually. It stops short of explicitly stating 'prefer this over the individual tools when you need the full package' or naming any exclusion.

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