Skip to main content
Glama

check_lc_documents

Checks letter-of-credit documents under UCP 600 rules to find discrepancies that cause bank rejection, tied to UCP articles with remedies.

Instructions

Will your letter-of-credit documents GET PAID? Banks reject roughly 60-70% of first-presentation documentary-credit submissions over DOCUMENTARY DISCREPANCIES. Give the fields of the credit + the presented documents (commercial invoice, bill of lading, insurance, packing list) and it applies the UCP 600 rules a trade-finance checker uses, returning the DISCREPANCIES that would make an examining bank reject the presentation — each tied to its UCP article with a remedy: invoice amount over the credit (art. 18/30 tolerances), currency mismatch (art. 18a), goods description not CORRESPONDING to the credit (art. 18c), data conflict across documents (art. 14), late shipment vs the latest-shipment date, STALE presentation (>21 days, art. 14c) or after expiry, port-of-loading/discharge mismatch on the B/L (art. 20), a non-clean B/L (art. 27), and insurance <110% of CIF / wrong currency / dated after shipment (art. 28). It reports clean-vs-rejected, the severity mix, what it checked and what it couldn't. Links to iter12 trade finance. ⚠️ The examining bank determines compliance under UCP 600 + ISBP 821 document-by-document; many discrepancies are judgement calls or waivable — MODELED pre-check, NOT a bank determination or legal advice (regla 7). PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
creditAmountNoThe credit (LC) amount.
creditCurrencyNoCredit currency (e.g. USD).
amountToleranceNoAmount tolerance fraction (e.g. 0.05 = ±5%). Default 0.
creditGoodsDescriptionNoGoods description as written in the credit.
portOfLoadingNoCredit's required port of loading.
portOfDischargeNoCredit's required port of discharge.
beneficiaryNoCredit beneficiary (the seller).
latestShipmentDateNoLatest shipment date (YYYY-MM-DD).
expiryDateNoCredit expiry date (YYYY-MM-DD).
presentationPeriodDaysNoPresentation period in days (UCP default 21).
incotermNoCredit incoterm (CIF/CIP trigger the insurance check).
insuranceRequiredNoDoes the credit require an insurance document?
invoiceAmountNoCommercial invoice amount.
invoiceCurrencyNoInvoice currency.
invoiceGoodsDescriptionNoGoods description on the invoice.
invoiceBeneficiaryNoWho issued the invoice.
blPortOfLoadingNoPort of loading on the B/L.
blPortOfDischargeNoPort of discharge on the B/L.
shipmentDateNoOn-board / shipment date on the B/L (YYYY-MM-DD).
presentationDateNoDate documents are presented to the bank (YYYY-MM-DD).
blCleanNoIs the B/L clean (no defect clause)?
insuredAmountNoInsured amount on the insurance document.
insuredCurrencyNoInsurance currency.
insuranceDateNoInsurance document date (YYYY-MM-DD).
packingListGoodsDescriptionNoGoods description on the packing list.
Behavior5/5

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

No annotations provided, so description carries full burden. It details the rule-based checking process, lists specific discrepancy checks, warns against treating it as a bank determination or legal advice, and mentions it returns severity mix and what couldn't be checked.

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?

The description is lengthy but front-loaded with a compelling question and key statistics. Every sentence adds relevant detail about capabilities, limitations, and pricing. Minor redundancy could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 25 parameters, no output schema, and no annotations, the description fully explains input requirements, the process, and output (discrepancies with UCP articles/remedies, clean/rejected status, severity mix). It even provides a legal disclaimer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 25 parameters. The description adds value by explaining how parameters are used in specific checks (e.g., invoice amount over credit, currency mismatch), tying them to UCP articles.

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?

The description clearly states it checks letter-of-credit documents under UCP 600 for discrepancies, listing specific rules checked and outputting discrepancies with remedies. It uniquely identifies this tool among siblings as specialized for LC document checking.

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 description implies use for pre-checking LC presentations before submission to a bank, mentioning premium pricing. It does not explicitly state when not to use or provide alternatives, but the specialized domain makes usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Baneado98/freight-pulse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server