Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Check trade document party consistency

trade-finance_document-party-consistency
Read-onlyIdempotent

Compare buyer, seller, applicant, beneficiary, shipper, and consignee fields across linked invoices, contracts, LCs, and documents. Price $0.04 USDC. POST /api/v1/trade-finance/document-party-consistency. 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_document-party-consistency"
  }
}

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.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
invoiceCountNoinvoiceCount. Number.
publicSourcesNopublicSources. Array.
amountInventedNoamountInvented. Boolean.
apiKeyRequiredNoapiKeyRequired. Boolean.
creditDecisionNocreditDecision. Boolean.
consistentCountNoconsistentCount. Number.
paidProviderUsedNopaidProviderUsed. Boolean.
financingApprovedNofinancingApproved. Boolean.
discrepancyInventedNodiscrepancyInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, it discloses the $0.04 USDC price and that an unpaid request returns x402 terms without executing the check. The endpoint adds invocation detail, but name normalization, matching strictness, and external-data behavior remain unexplained.

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?

The description front-loads the operation and then uses three short sentences for price, endpoint, and payment-gating behavior. It is compact, easy to scan, and contains no repetitive or promotional wording.

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?

The core task and payment behavior are covered, while the annotations and output schema reduce the prose burden. For a 13-parameter, deeply nested tool, however, the lack of minimum viable input, record-linking, input-mode, and comparison-semantics guidance leaves avoidable invocation uncertainty.

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 the baseline is 3. The description prioritizes the relevant party fields and core record collections, but adds no guidance on choosing among csv, json, text, file, and structured arrays, linking records by IDs, or using auxiliary parameters.

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 opening sentence specifies the operation, six party roles, and four linked trade-document resources, making the narrow consistency-checking purpose clear. It does not explicitly differentiate the tool from siblings such as document matching or LC discrepancy detection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The linked-document context implies use when validating party identities across a trade-finance package. There is no explicit when-to-use or when-not-to-use guidance, minimum-input condition, or direction to alternatives for related checks.

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