Skip to main content
Glama

Tariff Monitor: US Import Duty & HTS Lookup

Compare tariffs by origin country

compare_origins
Read-onlyIdempotent

Compare the estimated US import tariff for ONE HTS code across several origin countries side by side (e.g. China vs Vietnam vs Mexico vs India), for sourcing and "China plus one" decisions. For each origin returns the total current rate, the layers that make it up (MFN base, Section 301 China, Section 232 by HTS line, Section 301 Brazil, 2026 Section 301 forced-labor tariff) and the rate after the Section 301 China exclusions end (through 11:59 p.m. ET on 9 Jan 2027 per the Federal Register, FR Doc. 2026-22925), sorted lowest first, with the dollar duty when an annual import value is given. Estimates only; preferential rates (USMCA, FTAs) depend on rules of origin and are not assumed.

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": {
      "hts_code": "<hts_code>"
    },
    "name": "compare_origins"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. Entry date YYYY-MM-DD; the rate in force on that date is returned (e.g. "2027-01-09" vs "2027-01-10" to see the Section 301 exclusion end and the maritime duties). Default: today in US Eastern time.
hts_codeYesHTS code, 6 to 10 digits (e.g. "8471.30" or "6404112030"). Use lookup_hts_code first if you only have a product name.
origin_countriesNoISO-2 origin country codes to compare, 2 to 8 of them (e.g. ["CN","VN","MX","IN"]). Default: CN, VN, MX, IN, TH.
annual_import_value_usdNoOptional. Annual import value in USD; adds the estimated annual duty for each origin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional. Entry date YYYY-MM-DD; the rate in force on that date is returned (e.g. \"2026-11-09\" vs \"2026-11-10\" to see the Section 301 exclusion end and the maritime duties). Default: today in US Eastern time."New value: +"Optional. Entry date YYYY-MM-DD; the rate in force on that date is returned (e.g. \"2027-01-09\" vs \"2027-01-10\" to see the Section 301 exclusion end and the maritime duties). Default: today in US Eastern time."
  2. Changed1 schema field changed
    • addedInput schema / properties / date
      Added value: +{
      +  "description": "Optional. Entry date YYYY-MM-DD; the rate in force on that date is returned (e.g. \"2026-11-09\" vs \"2026-11-10\" to see the Section 301 exclusion end and the maritime duties). Default: today in US Eastern time.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavior beyond them: the exact return payload (total rate, component layers, post-exclusion rate), the sort order (lowest first), the conditional dollar-duty output when an annual value is supplied, and the precise exclusion expiry with a Federal Register citation. It also sets accuracy expectations ('Estimates only') so the agent knows results are modelled, not binding.

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 purpose is front-loaded in the first clause and the detail that follows is substantive rather than filler. It is dense and runs long, with the Federal Register document number and the exact 11:59 p.m. ET cutoff being borderline verbosity, but those details do support the exclusion-date claim.

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?

There is no output schema, so the description carries the full burden of describing the return value — and it does: the total rate, the component layers, the post-exclusion rate, the sort order, and the conditional duty amount. Combined with the estimate-only disclaimer and the exclusion end date, an agent has everything needed to call it and interpret results.

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 is already documented, and the description mostly restates the schema's semantics (one HTS code, multiple origins, annual value adds dollar duty). It adds only marginal framing — that origins are compared per single code and results are ranked — 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 and resource — compare the estimated US import tariff for ONE HTS code across several origin countries — and pins the scope with an example (China vs Vietnam vs Mexico vs India). The 'ONE HTS code' constraint and 'side by side' framing distinguish it from calculate_tariff without needing to open either schema.

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?

Names the decision context (sourcing and 'China plus one') which tells the agent when this tool is the right call, and adds an explicit scope caveat that preferential rates (USMCA, FTAs) are not assumed. It does not explicitly say when to prefer calculate_tariff over this tool, so the routing guidance is clear but not exhaustive.

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.