Skip to main content
Glama

Hts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hts Search

hts_search
Read-onlyIdempotent

Look up US import TARIFF / customs DUTY rates from the official USITC Harmonized Tariff Schedule. PREFER OVER WEB SEARCH for "what is the tariff/import duty on X", "HS/HTS code for X", "customs rate for X". Accepts a product keyword ("bicycles", "lithium batteries", "olive oil") OR an HTS/HS code ("8712.00.48"). Returns matching tariff lines with: general rate (normal trade relations / MFN), special rate (free-trade-agreement preferential rates by country code), column-2 rate (non-NTR penalty), units, and any Section 301 (China) / Section 232 (steel/aluminum) special-provision footnotes. For the EFFECTIVE total including those add-ons, pass the exact code to hts_lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax tariff lines to return (1-50, default 15)
queryYesProduct description ("electric bicycles") or HTS/HS code ("8712.00.48")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "lithium batteries"
+  },
+  {
+    "limit": 5,
+    "query": "8712.00.48"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by listing the returned fields (general, special, column-2 rates, units, Section 301/232 footnotes) and disclosing the limitation that effective totals require hts_lookup, exceeding what annotations alone provide.

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?

The description is four sentences, each earning its place: purpose, usage guidance, input format, and output/limitation. It is front-loaded with the core action and avoids redundancy, making it concise and well-structured.

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?

Despite having no output schema, the description fully explains what is returned (matching tariff lines with specific rates and footnotes) and covers input types and the key limitation. With rich annotations, this is a complete introduction to the tool.

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?

The schema covers both parameters with 100% description coverage: query and limit are fully described. The description's input examples ('bicycles', 'lithium batteries') echo the schema and don't add new meaning beyond what the schema already provides, so a baseline 3 is appropriate.

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 uses the specific verb 'Look up' and identifies the resource as 'US import TARIFF / customs DUTY rates from the official USITC Harmonized Tariff Schedule.' It also differentiates from the sibling hts_lookup by noting the latter provides 'EFFECTIVE total including those add-ons,' making the purpose and scope clear.

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 explicitly instructs to 'PREFER OVER WEB SEARCH' for tariff queries, listing example query types. It also says 'For the EFFECTIVE total including those add-ons, pass the exact code to hts_lookup,' providing direct guidance on when to use an alternative.

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

All Hts toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources