hts-classify
Server Details
Classifies products into HS/HTS customs codes for import/export workflows. $0.03/call via x402.
- 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.8/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity or confusion with other tools.
With a single tool, naming is trivially consistent; the imperative verb 'classify' clearly describes the action.
A single tool is appropriate for the narrow, focused purpose of classifying product descriptions into HS/HTS codes.
The tool fully covers the core functionality implied by the server name, including deterministic retrieval and confidence scoring, and explicitly notes its limitations.
Available Tools
1 toolclassifyAInspect
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?
With no annotations provided, the description carries full burden. It describes the operation as 'deterministic BM25 retrieval' and lists return fields, implying a safe, read-only nature. It explicitly states 'Not a customs ruling', adding transparency. No contradictions; however, it does not explicitly confirm no side effects or auth requirements.
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 is three sentences, front-loaded with purpose, method, and output details, followed by a disclaimer. No superfluous information; each sentence adds value.
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?
The description covers the tool's output and disclaimer but omits parameter details and prerequisites. Given no output schema, the return fields are described. However, the lack of parameter semantics reduces completeness for a tool with two parameters (one optional nested object).
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 coverage is 0% and the description offers no explanation of parameters. 'description' is required but no guidance on what constitutes a valid product description. 'options.top_k' and 'options.origin_hint' are entirely undocumented. Users must rely on parameter names alone, which is insufficient.
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?
The description clearly states the tool's purpose: 'Classify a product description into candidate HS/HTS10 tariff codes.' It specifies the verb 'classify', the resource 'product description', and the domain 'HS/HTS10 codes', with details on the retrieval method (BM25) and output elements (parent-chain, duty rate, confidence). This is specific and distinguishes it from generic classification tools.
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 implicitly indicates usage for obtaining tariff code candidates and includes a disclaimer that it is not a customs ruling, advising verification with a licensed broker. It lacks explicit when-not-to-use notes or alternative tool comparisons, but the disclaimer provides sufficient context for appropriate use.
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!