HTS Classify
Server Details
Maps a product name or description to Harmonized System / HTS customs classification codes — the lookup customs brokers, import/export compliance teams, and trade-automation agents need before filing a shipment or estimating duty. Returns ranked HS/HTS candidates. Pay-per-call via x402 (USDC on Base): $0.03/call, no account or API key. tools/list and /openapi.json are free for discovery.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or confusion between tools.
A single tool named 'classify' is inherently consistent; no naming conflicts or pattern violations exist.
One tool is borderline; it covers the core classification task but lacks supplementary tools like batch or code listing, making it thin for broader use cases.
The classify tool returns comprehensive information (parent chain, duty rate, confidence) and includes a disclaimer, covering the primary need. Minor gaps like batch processing or code lookup without classification exist but are not critical.
Available Tools
1 toolclassifyBInspect
Classify a product description into candidate HS/HTS10 tariff codes. Deterministic BM25 retrieval over the USITC HTS schedule with heading-agreement boosting, returning the full parent-chain description, general duty rate, and a score-gap confidence per candidate. Not a customs ruling — always includes a disclaimer to verify with a licensed broker.
| Name | Required | Description | Default |
|---|---|---|---|
| options | No | ||
| description | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the retrieval algorithm (BM25 with heading-agreement boosting), the deterministic nature, and the return content (parent-chain description, duty rate, score-gap confidence). The disclaimer about legal authority adds important context. Minor omission: no mention of output structure or potential errors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise sentences. The first sentence efficiently covers purpose, method, and return content. The second adds critical usage caution. No redundant information. Slightly dense but effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no sibling tools, the description covers the core functionality, algorithm, and return items. However, it lacks explanation of input parameters and does not describe error handling or edge cases. The disclaimer adds completeness for legal context but misses operational details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate but does not. The input schema has two parameters: 'description' (required string, maxLength 500) and 'options' (object with 'top_k' integer and 'origin_hint' string). The description never explains these parameters, their meaning, or constraints. This is a significant gap for correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'classify' and resource 'product description into candidate HS/HTS10 tariff codes'. Specific method (BM25 retrieval over USITC HTS schedule) and deterministic nature are mentioned, making the purpose distinct. No sibling tools to compare, but purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes a disclaimer that it is not a customs ruling and advises verification with a licensed broker, indicating it should be used for preliminary classification only. However, it does not explicitly state when to use vs alternatives or when not to use it, missing opportunity for clearer guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!