Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Look up US HTS duty rates

trade-tariff_us-hts-duty-rate-lookup
Read-onlyIdempotent

Return the published HTSUS General, Special and Column 2 rate columns, units and Chapter 99 cross-references for an HTS code from the vendored USITC release. Not a classification or additional-duty calculation. Price $0.02 USDC. POST /api/v1/trade-tariff/us-hts-duty-rate-lookup. An unpaid call returns the x402 payment terms and does 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": {
      "hts": "<hts>"
    },
    "name": "trade-tariff_us-hts-duty-rate-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsYeshts, string. Required.
programNoprogram, string. Optional.

Output Schema

NameRequiredDescriptionDefault
htsNohts. String.
pathNopath. Array.
foundNofound. Boolean.
unitsNounits. Array.
column2Nocolumn2. String.
generalNogeneral. String.
releaseNorelease. Object.
sourcesNosources. Array.
specialNospecial. Object.
childrenNochildren. Array.
rateLineNorateLine. String.
footnotesNofootnotes. Array.
descriptionNodescription. String.
limitationsNolimitations. Array.
programEligibleNoprogramEligible. Boolean.
chapter99ReferencesNochapter99References. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, and the description adds the details they cannot: a per-call price of $0.02 USDC, the HTTP POST endpoint, and — critically — that an unpaid call returns x402 payment terms and does not execute. That payment-gating behavior is exactly the kind of trait an agent must know before calling.

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 return payload, then exclusions, then price/endpoint/payment behavior — a sound ordering with no filler. The sentence fragments ("Not a classification or additional-duty calculation.") are efficient but read telegraphically; nothing is wasted, though the block could be slightly more cohesive.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description still covers source provenance, scope boundaries, cost, transport and payment failure mode. The only residual gap is the semantics of `program`, which is minor for a two-parameter lookup.

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 100%, so the baseline is 3, and the schema's own text for both params is just the name plus type. The description says the code identifies an HTS entry, but it never explains what the optional `program` selector does (presumably a Special-program indicator) or what happens with a malformed code. Meaning added beyond the schema is minimal.

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 a precisely enumerated resource: the HTSUS General, Special and Column 2 rate columns, units and Chapter 99 cross-references for an HTS code. It also names the source (vendored USITC release) and explicitly scopes out adjacent tasks ("Not a classification or additional-duty calculation"), which distinguishes it from sibling tariff tools without their names being listed.

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 exclusions give real routing guidance: an agent needing classification or an additional-duty computation knows to go elsewhere. It stops short of naming a concrete alternative sibling for those cases, so it is a clear context statement rather than a full when/when-not map.

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