Skip to main content
Glama

Zentria Flow

Search HTSUS lines

hts_search
Read-onlyIdempotent

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 observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results come from official HTSUS descriptions and hits are candidate-level, not authoritative rulings — an important epistemic caveat an agent would otherwise miss. It stops short of saying how many hits are returned or how they are ranked.

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, each doing distinct work: what it finds, what to use it for, and the caveat about result reliability. The purpose is front-loaded and there is no filler.

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 one-parameter, read-only lookup with full schema coverage and no output schema, this covers intent, input forms, downstream use, and result trustworthiness. Only minor gaps remain, such as result count or behavior on zero matches.

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?

With a single parameter at 100% schema coverage, the baseline is already met by the schema's examples. The description still adds value by framing the query as accepting either product words or a bare code prefix, reinforcing that two distinct input forms are valid.

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?

Uses a specific verb ('Find') with a precise resource ('US tariff lines (8-digit HTSUS codes)') and states the two accepted input modes: product words or a code prefix. The closing sentence distinguishing a search hit from a classification ruling further sharpens what this tool is and is not, versus siblings like us_tariff_check.

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 routes the agent: 'Use it to get a code for us_tariff_check,' naming the downstream sibling and the condition that selects it. It also implies a when-not via 'A search hit is a candidate, not a classification ruling,' though it never states outright when to skip this tool or what to do if no hit is found.

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.