Skip to main content
Glama
SoapyRED

FreightUtils MCP Server

by SoapyRED
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

hs_code_lookup

Find Harmonized System (HS) tariff codes for products to determine customs classifications and duty calculations. Search by product description or browse by code hierarchy.

Instructions

Search 6,940 Harmonized System (HS) tariff codes.

HS codes are 6-digit international product classification codes used for customs declarations and duty calculations. The first 2 digits = chapter, 4 digits = heading, 6 digits = subheading.

Use this tool when you need to:

  • Find the HS code for a product (e.g., "laptop", "olive oil")

  • Get the tariff classification hierarchy (section → chapter → heading → subheading)

  • Browse HS sections (I through XXI)

Provide a search term for description-based search, or an exact HS code for detailed lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch by product description (min 2 chars)
codeNoExact HS code lookup (2-6 digits)
sectionNoBrowse by section (Roman numeral, e.g., "II")

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Without annotations, description effectively discloses data scope (6,940 codes), hierarchy structure (section→subheading), and digit semantics.

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?

Well-structured with front-loaded purpose, concise domain explanation, and scannable bullet points; no redundancy.

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?

Comprehensive for input domain despite missing output schema; explains HS code system sufficiently for agent to interpret results.

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?

Despite 100% schema coverage, adds critical logical context that parameters are mutually exclusive (search term OR exact code OR section).

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?

Specific verb-resource ('Search HS tariff codes') clearly distinguishes from logistics/calculator siblings (cbm_calculator, container_lookup, etc.).

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?

Explicit 'Use this tool when' section with three concrete scenarios and parameter usage patterns, though lacks explicit exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SoapyRED/freightutils-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server