Skip to main content
Glama

Triplicate – export documents

Search HS codes

lookup_hs_code
Read-only

Use when a user asks which HS code a product falls under or what a code means. Search the HS 2022 nomenclature (6-digit international level) by English product description or by code prefix. Returns candidate codes with chapter and heading text. Codes are suggestions to confirm in the destination country's tariff, not rulings.

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": "lookup_hs_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesEnglish description (e.g. 'face cream', 'cotton t-shirts') or a code prefix (e.g. '3304')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false; the description adds real value beyond that by disclosing the fixed corpus (HS 2022, 6-digit), the shape of results ('candidate codes with chapter and heading text'), and the critical epistemic caveat that these are not binding rulings. It does not mention result volume or how the limit behaves, which keeps it from a 5.

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 sentences, all load-bearing: trigger first, then what is searched and how, then the accuracy caveat. No restatement of the tool name or 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?

With no output schema, the description carries the return-value burden and does so ('candidate codes with chapter and heading text'). Scope, trigger, and the ruling caveat are all present; the only gap is the undocumented limit parameter for a two-parameter 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?

Schema coverage is 50%: the query parameter is documented in the schema, and the description largely echoes it while adding the '6-digit international level' constraint. The limit parameter has a default but no description anywhere, and the description does not explain its role, so it does not fully compensate for the coverage gap.

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?

States a specific verb and resource ('Search the HS 2022 nomenclature') plus the exact scope ('6-digit international level') and the two lookup modes (product description or code prefix). This clearly separates it from lookup_port_code and the calculation/document siblings, which cover different domains entirely.

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?

The opening 'Use when a user asks which HS code a product falls under or what a code means' gives an explicit trigger, and the closing sentence warns the results are suggestions to confirm in the destination country's tariff. It stops short of naming alternatives or stating when not to use it, but no sibling is close enough to require that routing.

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.

Resources