Skip to main content
Glama

BRAINIAC Freight & Customs

Suggest HS code candidates

freight-customs_hs-code-candidate-suggest

Search the public UK Trade Tariff for commodity candidates matching a goods description. The result is not a customs classification and does not state a duty. Price $0.06 USDC. POST /api/v1/freight-customs/hs-code-candidate-suggest. Unpaid calls return 402 and do not run.

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": {
      "description": "<description>"
    },
    "name": "freight-customs_hs-code-candidate-suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
hsCodeNo
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses the price ($0.06 USDC), the payment failure mode (unpaid calls return 402 and do not run), the endpoint, and that results carry no duty and are not a binding classification. The main remaining gap is what a successful response contains — count, ranking, confidence — which an agent cannot infer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then caveats, price, endpoint, and payment behavior — each sentence carries information. The raw POST path is marginally redundant for an agent that invokes via the tool interface, but it is short and harmless.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, single-purpose lookup tool this covers the essentials — what it searches, that it is not authoritative, cost, and failure behavior. It falls short on the undocumented `hsCode` parameter and on any hint of result shape, both of which matter for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only covers one of two: `description` is described as the goods description to match. The `hsCode` parameter (4-14 chars) is never mentioned, so an agent cannot tell whether it is a filter, a seed hint, or a required prefix.

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 and resource: 'Search the public UK Trade Tariff for commodity candidates matching a goods description.' It is unmistakably distinct from the sibling validate/extract/calculate tools, and the disclaimer 'not a customs classification and does not state a duty' further pins down what kind of answer it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage context (you have a goods description and want candidate HS codes) and warns the output is not a classification, which is a partial when-not-to-rely-on-it note. It never states when to pick this over another approach, nor what to do with the candidates afterwards (e.g., confirm with a classification tool).

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