Skip to main content
Glama

Landed cost of a shipment

landed_cost
Read-only

Calculate a shipment's full landed cost across product value, freight, insurance, duties, VAT/GST and fees for 70+ countries, so you can estimate import charges before purchase or pricing decisions.

Instructions

Full landed cost of one shipment from the Zentria Flow keyed API: product value, freight, insurance, every duty layer, VAT/GST and fees, for 70+ countries. Needs the ZENTRIA_API_KEY environment variable (an API plan; the Sandbox plan is free). Each call counts against the plan quota. Planning estimate, not a customs ruling.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hs_code": "<hs_code>",
      "origin_country": "<origin_country>",
      "unit_value_usd": "<unit_value_usd>"
    },
    "name": "landed_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
hs_codeYesHS or HTS code, at least 4 digits, e.g. "6109.10.00".
currencyNoISO 4217 currency of the result. Default "USD".
quantityNoNumber of units. Default 1.
weight_kgNoOptional total weight in kg. Default: 0.5 kg per unit.
origin_countryYesISO-2 code of the origin, e.g. "CN".
transport_modeNoDefault "sea".
unit_value_usdYesValue of one unit in US dollars.
freight_cost_usdNoOptional freight quote in US dollars. Default: the engine's estimate.
destination_countryNoISO-2 code of the destination. Default "US".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: a required ZENTRIA_API_KEY environment variable, quota consumption per call, and the planning-estimate caveat. This is meaningful disclosure not present in structured fields.

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?

Three compact sentences, front-loaded with the core purpose, followed by prerequisites/quota and then the disclaimer. Every sentence carries distinct, actionable information with no filler.

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?

For a 9-parameter, fully documented calculation tool with no output schema, the description explains what the result contains and the key operational constraints (API key, quota, estimate-only nature). The only minor gap is no indication of result shape or units beyond the cost components listed.

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 every parameter already carries its own documentation including defaults and formats. The description adds no per-parameter detail (e.g., how freight_cost_usd interacts with the engine estimate), so the schema does the heavy lifting and 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 description states a specific verb+resource ('Full landed cost of one shipment') and enumerates the cost components (product value, freight, insurance, duties, VAT/GST, fees) plus coverage (70+ countries). It never explicitly differentiates itself from siblings like compare_origins or us_tariff_check, so it stops short of a 5.

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 closing line 'Planning estimate, not a customs ruling' implies the intended use case (pre-shipment planning), but there is no explicit when-to-use or when-not guidance relative to compare_origins or us_tariff_check. Usage is implied rather than stated.

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