Zovo Tariff Code Finder

Search HTS codes

search_hts_codes

Read-onlyIdempotent

Use this when the user wants a US HTS code, harmonized tariff code or import duty rate for a product, by product words or by a code prefix. Returns ranked 10-digit codes from the current USITC schedule with the description path, general, special and column 2 rates and units, plus a PDF classification worksheet and CSV. Does not decide the final classification and does not include Chapter 99 additional duties. Do not use for other countries' tariffs.

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": {
      "query": "<query>"
    },
    "name": "search_hts_codes"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Product words (1 to 6 words, at most 80 characters) or an HTS code prefix of 4, 6, 8 or 10 digits, e.g. wool sweater or 8712.00.
`max_results`	No	How many ranked codes to return, 1 to 25, e.g. 10 (default).

Output Schema

Name	Required	Description	Default
`notes`	Yes
`query`	Yes
`shown`	Yes
`limits`	Yes
`source`	Yes
`status`	Yes
`message`	Yes
`results`	Yes
`downloads`	Yes
`query_type`	Yes
`results_count`	No
`total_matches`	Yes
`headings_checked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (current USITC schedule), the ranked 10-digit output shape, the attached PDF/CSV artifacts, and the two explicit coverage limits (no final classification, no Chapter 99 duties).

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?

Front-loaded with the trigger condition and scoped tightly; the exclusion clause at the end is well placed. The enumeration of return fields (description path, rates, units, PDF, CSV) is somewhat redundant given an output schema exists, costing a little economy.

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?

For a two-parameter read-only lookup with full schema coverage and an output schema, the description covers the remaining burden: data source, ranking behavior, known limitations, and cross-jurisdiction exclusion. Nothing an agent needs in order to call it correctly is 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 coverage is 100%, and the schema already documents word count, character limits, and valid code prefix lengths with examples. The description restates the two input modes but adds no format or edge-case detail beyond the schema, 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 — retrieving US HTS codes, harmonized tariff codes, or import duty rates — and names the two input modes (product words or code prefix). It also implicitly separates itself from estimate_landed_cost by scoping to classification lookup rather than cost computation.

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?

Gives an explicit trigger ('Use this when the user wants...'), explicit exclusions ('Do not use for other countries' tariffs', 'Does not decide the final classification', no Chapter 99 duties), and implies the handoff to the landed-cost sibling. An agent knows both when to call it and when to stop.

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

All Zovo Tariff Code Finder 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?