Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Assess export payment term risk

trade-finance_export-payment-term-risk
Read-onlyIdempotent

Label supplied payment terms as lower, moderate, higher, or unclassified from wording only. Not a credit decision. Price $0.03 USDC. POST /api/v1/trade-finance/export-payment-term-risk. 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_export-payment-term-risk"
  }
}

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.
itemCountNoitemCount. Number.
higherCountNohigherCount. Number.
limitationsNolimitations. Array.
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

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, and the description adds genuinely new behavior: a $0.03 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms without running. That payment-gate disclosure is exactly the kind of trait annotations cannot express. It doesn't describe rate limits or whether results are cached, hence not a 5.

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?

Four short sentences, front-loaded with the action and output, followed by the caveat, price, and endpoint. Nothing is redundant and nothing important is buried.

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 the payment gating and read-only nature are covered. The only gap is guidance on which of the many optional input representations (text, csv, json, file, and the structured arrays) should be used, which matters for a 13-parameter tool.

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 schema already documents all 13 optional parameters, and the description adds nothing per-parameter. 'From wording only' hints that the text/csv/json/file content carries the terms, but the relationship between the 13 input forms (which to supply, whether they can be combined) is left entirely to the schema.

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?

Opens with a specific verb ('Label') and resource ('supplied payment terms'), and names the exact output labels (lower, moderate, higher, unclassified). An agent immediately knows what comes out of the call, which is rare and valuable.

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?

'From wording only' and 'Not a credit decision' clearly bound the scope and rule out credit-underwriting use, implicitly steering toward credit-exposure-calculate. It does not name that sibling explicitly or state when an agent should skip this tool, so it stops short of a 5.

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