Skip to main content
Glama

Search the US tariff schedule (HTS) by number or words

tariff_us
Read-only

US HTS lines from the USITC HTS REST API: HTS number, description, general, special and column 2 rates, units and footnotes. Look up by number (hts, e.g. 8471.30) or search words (q; every word must appear in the description). Chapter 99 lines (extra duties such as Section 301 or 232) come back separately. A blank rate on a statistical line means the rate is set on its parent heading. Up to 25 lines. Public domain. Related tools on this server, for a different need: tariff_uk when you need to return UK Global Tariff data for a 6–10-digit commodity. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tariff_us"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to find in descriptions, e.g. portable data processing (every word must appear)
htsNoHTS number or prefix, e.g. 8471.30 or 8471300100
limitNoLines to return, 1 to 25, default 10

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
queryNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo
additionalDutiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / additionalDuties
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations only declare readOnlyHint and openWorldHint, but the description adds the 25-line cap, the fact that Chapter 99 lines (Section 301/232) come back separately, the blank-rate-means-parent-heading quirk, public-domain status, and the x402 pricing model with failed calls free. These are real behavioral traits an agent can't get from the annotations.

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?

Content is front-loaded with the data source, fields, and lookup modes before the caveats and pricing. It is dense but nearly every sentence carries information; the pricing/payment sentence is the longest and only marginally useful at selection time.

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?

An output schema exists, so return values needn't be explained, and the description covers the remaining gaps: data quirks (Chapter 99, blank statistical rates), result cap, and cost model. Nothing needed to invoke it correctly appears missing.

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, including the 'every word must appear' rule and the 1–25 limit. The description mostly restates those semantics and adds little syntax or format detail, so the baseline of 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?

The description names a specific resource (US HTS lines from the USITC HTS REST API), the exact fields returned, and the two lookup modes (hts number/prefix vs. q search words). It also explicitly distinguishes itself from the sibling tariff_uk tool, so an agent can pick it without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use each lookup mode ('Look up by number (hts, e.g. 8471.30) or search words (q; every word must appear)') and routes the agent elsewhere for a different need ('tariff_uk when you need to return UK Global Tariff data for a 6–10-digit commodity'). Both the when-to-use and the alternative are explicit.

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