Skip to main content
Glama

Tariff Monitor: US Import Duty & HTS Lookup

Calculate US import tariff

calculate_tariff
Read-onlyIdempotent

Calculate the full stacked US import tariff rate for an HTS code from a specific origin country. Returns: base rate, each additional layer (China Section 301 matched by HTS line to Lists 1, 2, 3, 4A and the 2024 four-year-review increases; Section 232 steel, aluminum and copper matched by HTS line to the U.S. note 16 lists, headings 9903.82.02-.26: 50% on listed metal articles, 25% on listed derivatives, UK and 15%-floor rates, with the metal-content conditions stated; other Section 232 programs (vehicles and parts, wood products, trucks, semiconductors, drones) flagged as needs review when the line is named, not computed; Section 301 Brazil, 25% since 22 Jul 2026, heading 9903.05.01, with its exemption lists; and the 2026 Section 301 forced-labor tariff on 60 economies: 10% or 12.5% by origin, or a 10%/12.5% cap net of MFN for the EU, Taiwan, Japan, South Korea and Switzerland, in effect since 24 Jul 2026, FR Doc. 2026-15181, HTS 9903.05.20-9903.05.84), the total current rate, the date the data was checked, and notes naming each exemption or assumption (Section 232 goods, USMCA- or CAFTA-DR-qualifying entries, listed products). For products of Canada it notes that Section 338 duties may apply; their product lists are published only as images, so they are not computed. Also states when the Section 301 China product exclusions end: through 11:59 p.m. ET on January 9, 2027 (Federal Register, FR Doc. 2026-22925, which extended the earlier 9 Nov 2026 end). Rates are effective-date aware: pass date (YYYY-MM-DD) for the rule in force on that entry date. For products of China it applies the 178 Section 301 product exclusions by statistical number (U.S. note 20(vvv)/(www)) through their end date, and the maritime Section 301 headings (9903.92.10 +25% on ship-to-shore cranes; from 10 Jan 2027 (the maritime action is suspended through 9 Jan 2027 by FR Doc. 2026-22867) 9903.91.14 +100% on those cranes and 9903.91.12 +100% on intermodal chassis, shown as "up to" because chapter 99 does not say how it combines with List 3), each with its legal source, and says when a rate depends on a proposed, not final, extension. Figures are estimates; IEEPA tariffs ended 20 Feb 2026 and are not included. Optionally computes dollar impact from annual import volume.

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": "calculate_tariff"
  }
}

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 — at least 6 digits, up to 10 (e.g. "6404.11" or "6404112030"). Dots and spaces are ignored. Zero-padded headings such as "6404110000" are not real schedule codes; if the exact code is not found, the 8- then 6-digit heading is tried and the answer states which code the rate is for.
origin_countryNoISO-2 origin country code (e.g. "CN" for China, "VN" for Vietnam, "MX" for Mexico). Default: CN.CN
annual_import_value_usdNoOptional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and any additional cost once the Section 301 China exclusions end (after 11:59 p.m. ET on January 9, 2027 per the Federal Register, FR Doc. 2026-22925).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / annual_import_value_usd / description
      Previous value: -"Optional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and any additional cost once the Section 301 China exclusions end (after 11:59 p.m. ET on January 9, 2027 per the Federal Register; USTR's press release says November 10, 2026)."New value: +"Optional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and any additional cost once the Section 301 China exclusions end (after 11:59 p.m. ET on January 9, 2027 per the Federal Register, FR Doc. 2026-22925)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / annual_import_value_usd / description
      Previous value: -"Optional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and any additional cost once the Section 301 China exclusions end (after 11:59 p.m. EDT on November 9, 2026 per the Federal Register; USTR's press release says November 10, 2026)."New value: +"Optional. Your annual import value in USD. If provided, the response includes the dollar cost of current duties and any additional cost once the Section 301 China exclusions end (after 11:59 p.m. ET on January 9, 2027 per the Federal Register; USTR's press release says November 10, 2026)."
    • 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."
  3. 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"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, which already mark this as read-only, idempotent, open-world, and non-destructive, the description discloses the returned rate layers, assumptions, exclusions, non-computed programs, effective-date behavior, and estimate status. It also names specific legal sources and limitations, giving the agent unusually rich behavioral context.

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 purpose is front-loaded, but the description is a dense single paragraph packed with legal citations, heading numbers, and nested caveats. Much of the detail is useful for transparency, yet the structure is harder to scan than necessary and repeats some schema-level parameter guidance.

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 must explain return values, and it does so thoroughly: base rate, additional layers, total rate, data-check date, and assumption notes. Given the complexity of stacking tariff programs, the definition is complete enough for an agent to understand what it will receive.

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%, and the schema already explains the HTS code format, date semantics, origin default, and annual import value. The description reinforces date-aware behavior and optional dollar impact, but adds little parameter meaning beyond what the schema already provides.

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?

The first sentence states a specific verb and resource: calculate the full stacked US import tariff rate for an HTS code from a specific origin country. This is clearly distinct from classification, lookup, or comparison tasks implied by the sibling names, and the agent can identify the tool without opening the schema.

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 establishes the operating context, including HTS code, origin country, entry date, and optional dollar impact. However, it never explicitly says when to use this rather than lookup_hts_code or compare_origins, and it gives no when-not conditions, so usage is mostly implied by the purpose.

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.