Skip to main content
Glama

payment_terms

For import deals, assesses counterparty relationship and country risk to recommend payment terms from cash-in-advance to open account, and prices letter of credit commissions.

Instructions

Recommend the TRADE-FINANCE / PAYMENT TERMS for an import deal — the other half of the transaction the freight tools ignore. Give the lane (→ exporter country at origin, importer country at destination), the invoice value and the counterparty RELATIONSHIP, and it scores the payment-instrument spectrum — CASH-IN-ADVANCE / LETTER OF CREDIT (irrevocable, possibly CONFIRMED) / DOCUMENTARY COLLECTION D/P (documents against payment) / D/A (documents against acceptance) / OPEN ACCOUNT — on its RISK ALLOCATION (CIA = all risk on the buyer … open account = all risk on the seller) and arrange cost, then recommends one by the relationship × COUNTRY-RISK matrix: a new counterparty in a high-risk importer country → an irrevocable, confirmed LC; an established relationship in a safe country → cheaper open account; in between → documentary collection. It PRICES the LC commission for the deal (issuing rises with importer-country risk; confirmation — a bank in the seller's country adding its guarantee — adds a country-risk-scaled premium), and ties to Incoterms (CIF/CIP put insurance on the seller; an LC pairs with the FOB/CFR document set). Country-risk and LC-commission bands are MODELED market-typical figures; this is not financial, legal or banking advice (regla 7). PREMIUM: x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port — its COUNTRY is taken as the exporter/seller country.
dest_portYesDestination port — its COUNTRY is taken as the importer/buyer country (drives the country-risk band).
invoice_valueYesCommercial invoice value in USD. REQUIRED — finance costs are priced on it.
container_typeNoContainer size '20ft'/'40ft'/'40HC'. Optional; defaults to '40ft'.
relationshipNoCounterparty relationship strength: 'new', 'developing' (default), 'established' or 'long-term'. The single biggest driver of the recommendation.
importer_countryNoOverride the importer ISO-2 country (else taken from the destination port).
exporter_countryNoOverride the exporter ISO-2 country (else taken from the origin port).
confirmedNoForce the LC pricing confirmed/unconfirmed. Optional; default = auto by importer-country risk.
incotermNoOptional Incoterms 2020 rule (CIF, FOB, CIP…) for the document-set tie-in note.
Behavior5/5

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

With no annotations, the description fully discloses behavior: scoring risk allocation, pricing LC commissions, tying to Incoterms, and noting that figures are modeled. It includes a disclaimer and mentions the premium mechanism.

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 the main purpose. Every sentence adds necessary detail for a complex tool. Could be slightly more concise but respects the complexity.

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?

For a 9-parameter tool with no output schema, the description covers inputs, logic, outputs, and limitations thoroughly. It explains the recommendation matrix, pricing, and ties to Incoterms, making it self-contained.

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?

All 9 parameters are described in the schema (100% coverage), but the description adds context such as the role of origin/dest ports for countries, relationship as the main driver, and default behaviors. This adds meaningful value beyond 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?

The description clearly states the tool recommends trade-finance/payment terms for import deals, explicitly distinguishing it from sibling freight tools. It details the payment instrument spectrum and the basis for recommendation.

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

Usage Guidelines5/5

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

The description specifies when to use (for import deals) and what inputs are required (lane, invoice value, relationship). It contrasts with sibling tools and provides a clear recommendation logic based on relationship and country-risk.

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