Skip to main content
Glama

BRAINIAC Trade Finance & Receivables Intelligence

Assess invoice financing readiness

trade-finance_invoice-financing-readiness
Read-onlyIdempotent

Score supplied invoices for completeness of identifiers, amounts, parties, and dates before you finance, assign, or pay a trade instrument. This is not a financing approval. Call with optional text, json, csv, file, parties, invoices and others. Returns checkedAt, invoiceCount, readyCount, items, creditDecision, financingApproved, amountInvented, discrepancyInvented. HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: text, csv, file, parties, invoices, contracts, lettersOfCredit, documents, assignments, worldBank, asOf, discountRatePct, checkedAt, invoiceCount, readyCount.

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_invoice-financing-readiness"
  }
}

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.
readyCountNoreadyCount. Number.
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

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses that HTTP 200 responses with status complete, partial, or failed are billed at full price while 4xx/5xx are not — genuinely useful cost behavior for an open-world tool. It also pre-empts misreading of the creditDecision/financingApproved output fields by stating the tool is not an approval. Remaining gaps are how the scoring itself is computed and whether calls with no input still incur a charge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tight and front-loaded with the core purpose and the key disclaimer, and the billing sentence earns its place. However, the 'Keywords:' trailer listing seventeen schema field names is pure repetition with no informational value, and 'Call with optional text, json, csv, file, parties, invoices and others' restates the schema vaguely.

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?

For a 13-parameter tool with nested objects, the description covers purpose, timing, billing, and return fields, and an output schema exists so return details need not be explained. But with zero required parameters it never says what happens on an empty call or which inputs are needed for a meaningful score, leaving a real operational gap.

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 every one of the 13 parameters including nested invoice, contract, document, and letter-of-credit fields. The description only re-lists parameter names as a keyword dump and adds no semantics such as which fields drive readiness scoring or how parties/invoices relate. 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?

The first sentence gives a specific verb and resource ('Score supplied invoices for completeness of identifiers, amounts, parties, and dates') and names the downstream decisions it feeds (finance, assign, pay). The explicit disclaimer 'This is not a financing approval' carves out a boundary against approval-style siblings. It stops short of naming which sibling handles the actual approval or discounting calculation.

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?

'before you finance, assign, or pay a trade instrument' states a clear usage context, which is more than most definitions offer. It also sets a negative boundary by declaring what the tool is not. It does not name an alternative tool to use when the agent actually wants a financing decision or discount computation.

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