Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

importers_paid

Read-onlyIdempotent

Review recent tariff rates paid on an HTS code by country over the latest three months, including base and Chapter 99 duties as a percent of value by month.

Instructions

What importers from a country actually paid on a code in the latest 3 months Census has published: base rate plus Chapter 99 duties (Section 301, 232 and the like), as a percent of value, by month. Not the duty a shipment will owe today (Census is about 2 months behind and the rules change), and anti-dumping/countervailing duties are not included. For "what will this cost", not for classifying.

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": {
      "code": "<code>",
      "country_of_origin": "<country_of_origin>"
    },
    "name": "importers_paid"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesAn HTS code, 6 to 10 digits, dotted or not (8205.51.30).
country_of_originYesCountry of origin: name, ISO code or common alias (China, CN, PRC, Viet Nam).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the data's composition (base rate plus Chapter 99 duties such as Section 301 and 232), the unit (percent of value, by month), the freshness (~2 months behind publication), and a material omission (anti-dumping/countervailing duties not included). Those are exactly the caveats an agent needs before quoting a number to a user.

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, each doing distinct work: definition and measurement, then two explicit exclusions. The core output metric (percent of value, by month) is front-loaded rather than buried.

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?

With an output schema present, return-value explanation is unnecessary, and the annotations already cover safety and idempotency. The description supplies the remaining non-obvious context: data lag, duty coverage, and the AD/CVD gap, leaving nothing an agent needs to call this correctly unstated.

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 both parameters (HTS code format, country name/ISO/alias handling) are already fully documented in structured fields. The description references "a code" and "a country" but adds no syntax, format, or edge-case meaning beyond the schema, so 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+resource: what importers from a country actually paid on a given HTS code, measured as a percent of value, by month, over the latest 3 published months. It also delineates what it is not (not today's duty, not AD/CVD, not classification), which separates it cleanly from siblings like classify_product and lookup_hts_code.

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 gives the use case ("For 'what will this cost'") and the exclusion ("not for classifying", "Not the duty a shipment will owe today"), so an agent knows both when to pick it and when to route elsewhere. The caveat that the rules change and Census lags ~2 months further scopes appropriate use.

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