Skip to main content
Glama

Total landed cost: item + fee + shipping + customs duties & import taxes

estimate_landed_cost
Read-onlyIdempotent

Estimates what a buyer pays in total to get US goods delivered: item price, optional US sales tax, GS Assisted Purchase fee, live GS shipping (if package weight given) and estimated import duty/VAT for the destination from a sourced rules table (Angola, Saudi Arabia, UAE, UK, Canada, Australia, Nigeria, Pakistan, India, Brazil, Germany, France, Netherlands). Returns a low–high range. Use for 'how much will it cost in total to buy X in the US and get it to ', 'customs duty / VAT / import tax on a US order'. Results are ESTIMATES, not quotes.

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": {
      "destination_country": "<destination_country>",
      "items_total_usd": "<items_total_usd>"
    },
    "name": "estimate_landed_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
hs_codeNoOptional HS code; used with Easyship's duty API when configured.
packageNoPackage for a live shipping quote.
shipping_usdNoKnown shipping cost. Omit and pass package to fetch live GS rates.
payment_methodNoHow the GS invoice will be paid. Bank transfer or crypto: 0% standard assisted-purchase fee.card
item_categoriesNoDistinct product types (EU €3-per-category duty). Default 1.
items_total_usdYesTotal price of the items in USD (all quantities).
us_sales_tax_pctNoUS sales tax % if the store charges it. Default 0 (GS address is in Delaware: no sales tax).
assisted_purchaseNo'standard' if GS buys it for you; 'none' if the shopper buys and ships to their GS address.standard
preferred_carrierNoPick the cheapest service of this carrier (DHL, FedEx, UPS, USPS).
destination_countryYesISO 2-letter code or country name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety bar is low. The description adds genuine context beyond them: shipping is only live when package weight is supplied, duties come from a sourced rules table limited to a named country list, and results are estimates rather than quotes. It does not say what happens for a destination outside that list, which is the main behavioral gap.

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 cost breakdown is front-loaded and the usage examples and estimate disclaimer follow in a logical order. The component enumeration sentence is long and dense but every clause carries information; only minor tightening is possible.

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 10-parameter tool with a nested package object and no output schema, the description does the important work: it explains the returned low–high range and lists supported destinations. Remaining gaps are the unsupported-country behavior and the units/currency of the returned range, but the agent has enough to call it correctly.

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 parameter including the nested package fields and enums. The description adds cross-parameter meaning — that supplying package weight is what triggers live shipping, and that sales tax is optional — but says nothing about item_categories, hs_code, or preferred_carrier, so the baseline 3 applies.

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?

States a specific verb (estimates) and resource (total landed cost) and then enumerates exactly what is included: item price, optional US sales tax, GS Assisted Purchase fee, live GS shipping, and import duty/VAT. The country list and the 'returns a low–high range' clause make it distinguishable from a plain shipping-rate lookup.

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?

Provides explicit trigger phrasings ('how much will it cost in total to buy X in the US and get it to <country>', 'customs duty / VAT / import tax on a US order'), which is clear when-to-use guidance. It stops short of naming alternatives such as get_shipping_rates for shipping-only questions or request_shipment_quote for firm quotes, so routing between siblings is only implied.

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.