Skip to main content
Glama

get_landed_cost

Calculate total landed cost for imports, breaking down FOB value, ocean freight, insurance, customs duty, and import VAT. Includes HS code classification and origin-sensitive trade remedies.

Instructions

Get the full LANDED COST (cost puesto en destino) of an import — the number the importer's margin actually depends on, not just the freight. Returns merchandise value (FOB) + all-in ocean freight (base + every surcharge) + insurance (CIF) + CUSTOMS DUTY + import VAT/consumption tax, as a line-item breakdown, plus the % of landed cost that is freight vs duties vs taxes. Includes an HS-CODE CLASSIFIER: pass a product description ('bluetooth earbuds', 'office chairs', 'cotton t-shirts') and it proposes the most likely HS6 heading with a confidence score (and 2-3 candidates when the text is ambiguous), or pass an explicit hs_code. Duty is modeled per destination bloc (US HTS, EU TARIC, UK Global Tariff, Canada, Australia, Japan) with the right MFN rate for the product family, then the ORIGIN-SENSITIVE trade remedies: US Section 301 applied ONLY to China-origin goods, Section 232 on steel/aluminium, an ANTIDUMPING/CVD flag on high-risk family×origin combos (it warns, it does not invent a rate), and FTA PREFERENCE (EVFTA, USMCA, CETA, EU-Japan EPA, RCEP, …) when origin↔destination share an agreement — subject to rules of origin. De-minimis is handled (US $800, EU €150, …): below threshold → no duty/tax. Import VAT is computed on the correct CIF+duty base (EU VAT by country; the US has no federal import VAT). Every figure is tagged typical/modeled; this is an INDICATIVE landed-cost estimate and HS-classification aid, NOT a binding customs ruling. PREMIUM: pay per call with x402 (USDC on Base) or set a prepaid key (FREIGHT_PULSE_KEY). Same UN/LOCODE port normalization as get_spot_rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
origin_portYesOrigin port (city name, UN/LOCODE, or 'City, Country'). The origin COUNTRY drives Section 301 / FTA / antidumping.
dest_portYesDestination port (city name, UN/LOCODE). The destination COUNTRY drives the duty bloc (US/EU/UK/CA/AU/JP) and import VAT.
productNoProduct description to classify, e.g. 'bluetooth earbuds', 'office chairs', 'cotton t-shirts', 'car tyres'. The classifier maps it to an HS6 heading. Provide this OR hs_code.
hs_codeNoExplicit HS code (6+ digits, e.g. '851830'). Overrides the text classifier. Provide this OR product.
fob_valueYesMerchandise value (FOB) in USD — the goods value at origin. REQUIRED: duties & taxes are computed on this (via CIF).
container_typeNoContainer size '20ft'/'40ft'/'40HC' for the freight leg. Optional; defaults to '40ft'.
ship_dateNoIntended ship date (ISO). Drives seasonal freight surcharges. Optional; defaults to today.
estimated_days_at_portNoDays the box will dwell at destination (adds Demurrage & Detention to the freight leg). Optional.
free_daysNoCarrier free days before D&D (default 5 if a dwell is given).
overweightNoFlag an overweight load (freight surcharge). Optional.
fuel_proxyNoOptional VLSFO $/tonne for the BAF model. Optional.
insurance_rate_pctNoMarine insurance as a fraction of FOB+freight for the CIF model (default 0.005 = 0.5%). Optional.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It thoroughly discloses the tool's behavior: returns indicative breakdown, HS classification, duty rules per destination/origin, de minimis thresholds, VAT computation, and caveats. This is comprehensive and sets accurate expectations.

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 description is long and detailed, packing a lot of information. While it is well-structured with clear sections, it could be more concise. Every sentence earns its place, but brevity could improve agent parsing.

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?

Given 12 parameters, no output schema, and no annotations, the description is remarkably complete. It covers all major aspects: output breakdown, classification, duty rules, VAT, de minimis, caveats, and even payment. It meets the needs for a complex estimation tool.

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 description coverage is 100%, but the tool description adds valuable context beyond field definitions, e.g., explaining that origin_port drives trade remedies and FTA logic. This helps the agent understand parameter significance in the broader computation.

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 description clearly states the tool returns a landed cost breakdown with HS classification and duty modeling. It covers a specific domain (imports) and many related concepts, but does not explicitly differentiate from siblings like total_cost_ownership or get_all_in_rate, leaving some ambiguity.

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 description explains what the tool returns and the components involved, implying it is for estimating landed costs. However, it lacks explicit guidance on when to use this versus alternatives (e.g., get_spot_rate for freight only) and does not mention exclusions or prerequisites.

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