Skip to main content
Glama

lookupHsTariffDuty

Classify products into 6-to-10 digit Harmonized System (HS/TARIC) customs codes and calculate import duty/VAT rates. Use when classifying physical goods into 6-to-10 digit Harmonized System (HS/TARIC) customs codes and calculating MFN import duty, Section 301 tariffs, VAT/GST rates, and de minimis thresholds between two countries. Do not use for courier shipping quotes (use getCourierShippingRates).

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": {
      "product_description": "<product_description>",
      "origin_country": "<origin_country>",
      "destination_country": "<destination_country>"
    },
    "name": "lookupHsTariffDuty"
  }
}

Input Schema

NameRequiredDescriptionDefault
origin_countryYes2-letter uppercase ISO country code of manufacture/export (e.g., CN, VN, MX).
destination_countryYes2-letter uppercase ISO country code of import customs destination (e.g., US, GB, DE).
product_descriptionYesSpecific material and functional description of the physical good for customs classification.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / destination_country / examples
      Added value: +[
      +  "US"
      +]
    • addedInput schema / properties / destination_country / pattern
      Added value: +"^[A-Z]{2}$"
    • addedInput schema / properties / origin_country / examples
      Added value: +[
      +  "CN"
      +]
    • addedInput schema / properties / origin_country / pattern
      Added value: +"^[A-Z]{2}$"
    • addedInput schema / properties / product_description / examples
      Added value: +[
      +  "lithium-ion portable power bank 20000mAh"
      +]
    • addedInput schema / properties / product_description / minLength
      Added value: +5
  2. Changed3 schema fields changed
    • changedInput schema / properties / destination_country / description
      Previous value: -"2-letter ISO importing country (e.g., UK, US, DE)"New value: +"2-letter uppercase ISO country code of import customs destination (e.g., US, GB, DE)."
    • changedInput schema / properties / origin_country / description
      Previous value: -"2-letter ISO country of manufacture (e.g., CN)"New value: +"2-letter uppercase ISO country code of manufacture/export (e.g., CN, VN, MX)."
    • changedInput schema / properties / product_description / description
      Previous value: -"Detailed description of the physical good (e.g., lithium-ion power bank, men cotton t-shirt)"New value: +"Specific material and functional description of the physical good for customs classification."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It usefully enumerates what the calculation covers (MFN duty, Section 301 tariffs, VAT/GST, de minimis thresholds), which is real context beyond the name, but it never addresses classification reliability, whether results are legally binding for customs declaration, or how ambiguity in the product description is handled. Read-only, no-side-effect nature is implied rather than stated.

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?

Front-loaded with the purpose, but the 'Use when...' sentence restates the first sentence almost verbatim ('classifying physical goods into 6-to-10 digit Harmonized System (HS/TARIC) customs codes and calculating... rates'), which is pure duplication. The only non-redundant new content is the rate-type list and the courier exclusion.

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?

With no output schema, the description does the work of telling the agent what comes back (HS code plus duty, tariff, VAT and de minimis figures) and the schema fully documents all three required parameters. Only the absence of any caveat on classification confidence or jurisdictional HS-vs-TARIC code version keeps it from being complete.

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 defines origin_country, destination_country and product_description fully. The description adds only the implication that exactly two countries are compared and that MFN/Section 301 rates depend on that pair, which is marginal beyond the schema. 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?

Names a specific verb (classify) plus a concrete resource (6-to-10 digit HS/TARIC customs codes) and the derived computation (import duty/VAT rates). The scope is instantly separable from siblings like getCourierShippingRates or getContainerFreightRates.

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?

Explicitly states when to use it (classifying physical goods, calculating MFN duty, Section 301 tariffs, VAT/GST, de minimis between two countries) and when not to, with a named alternative: 'Do not use for courier shipping quotes (use getCourierShippingRates)'. This is the full when/when-not/alternative pattern.

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.

Resources