Skip to main content
Glama

Search HTSUS lines

hts_search
Read-onlyIdempotent

Find US 8-digit HTSUS tariff codes by product words or partial code to obtain a candidate code for tariff checks; search results are not classification rulings.

Instructions

Find US tariff lines (8-digit HTSUS codes) by product words or the start of a code, from the official HTSUS descriptions. Use it to get a code for us_tariff_check. A search hit is a candidate, not a classification ruling.

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

Input Schema

NameRequiredDescriptionDefault
queryYesProduct words or the start of a code, e.g. "cotton t-shirt" or "6109".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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: results derive from official HTSUS descriptions and hits are non-authoritative candidates rather than rulings. It does not say how many hits are returned or how they are ranked, which is the remaining gap.

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 short sentences, front-loaded with what the tool does, followed by the workflow routing and the reliability caveat. Nothing is redundant or padded.

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?

For a single-parameter lookup tool with no output schema, the description covers purpose, input forms, downstream use, and result trust level. It stops short of describing the shape of a hit (code plus description, ordering), which would have made it fully self-sufficient.

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 query parameter already documents both accepted forms with examples ('cotton t-shirt', '6109'). The description restates the same words-or-code-prefix semantics, reinforcing but not extending what the schema 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?

States a specific verb and resource (find US tariff lines / 8-digit HTSUS codes) plus the two accepted query modes (product words or code prefix), and grounds the results in official HTSUS descriptions. An agent can distinguish this discovery tool from siblings like us_tariff_check 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 Guidelines4/5

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

Explicitly names the downstream tool and the reason to use this one: 'Use it to get a code for us_tariff_check.' It also bounds the output with 'a search hit is a candidate, not a classification ruling,' implicitly telling the agent not to treat results as a determination. No explicit statement of when not to use it, but the boundary is clear enough.

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