SiteCheck Trade & Energy

United States import duty lookup from the USITC Harmonized

logistics_customs_duty_calc

Read-only

United States import duty lookup from the USITC Harmonized Tariff Schedule: HTS codes matching a code prefix or keyword with general, special and column-2 rates, units, and the duty amount for a customs value in USD when the general rate is ad valorem. US tariff only; no VAT, no other countries. Related tools on this server, for a different need: logistics_customs_cbp_manifest when you need US import bills of lading for a company: the most recent; logistics_customs_broker_verify when you need to check a US customs broker against U.S. Customs and Border. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "logistics_customs_duty_calc"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	HTS code (e.g. 8541.10.00) or keyword (e.g. diodes)
`value`	No	Optional customs value in USD to compute the general duty

Output Schema

Name	Required	Description	Default
`lines`	No
`query`	No
`source`	No
`checkedAt`	No
`customsValueUsd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the data source (USITC HTS), the computation caveat that duty is only derived 'when the general rate is ad valorem', and a full commercial model: $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls not charged. That is exactly the payment/auth context an agent needs before invoking a metered endpoint.

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 sentences, each earning its place: capability and scope first, sibling routing second, pricing last. No repetition of the title, no filler, and the most decision-relevant constraint (US-only) is front-loaded with the capability statement.

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 an output schema present, return-value detail is unnecessary, and annotations already carry the safety profile; the description fills the remaining gaps (source, scope, computation condition, pricing). The only omission is any hint about result volume or pagination when a broad keyword matches many HTS codes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema documents both parameters; the description nonetheless adds real meaning — that 'q' supports prefix matching as well as exact codes and keywords, and that 'value' only yields a duty amount under a general ad valorem rate. It stops short of stating what happens with a non-ad valorem rate or multiple matches.

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 description names a specific verb and resource ('United States import duty lookup from the USITC Harmonized Tariff Schedule') and enumerates what is returned: HTS codes matching a prefix or keyword, general/special/column-2 rates, units, and computed duty. It also bounds scope explicitly ('US tariff only; no VAT, no other countries'), which separates it from the many non-US tariff siblings.

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?

It routes the agent away from two named siblings with conditions attached ('logistics_customs_cbp_manifest when you need US import bills of lading', 'logistics_customs_broker_verify when you need to check a US customs broker'), and the 'US tariff only, no other countries' clause implicitly excludes the EU TARIC, China, Japan, UK and WITS tariff siblings. The one unaddressed routing decision is the natural hand-off from logistics_hs_code_classifier (classify product → lookup rate), which is left implicit.

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

All SiteCheck Trade & Energy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?