tariff-resolver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hs_candidatesA | Returns top 8-10 digit HTS code candidates (with MFN/FTA rates and CBP CROSS ruling links) for a product description. Results are CANDIDATES for pre-broker screening, not a classification ruling. IMPORTANT: the HTS uses legal terminology, not trade names — BEFORE CALLING, rewrite the product description into HTS-style material + use nouns (e.g. 'pink kids backpack' → 'travel bags of man-made fibers'; 'water bottle' → 'vacuum flask' or 'bottle of plastics'). If you get 0 results, retry with 2-3 different phrasings. |
| calculate_tariff_scenarioA | Returns the HTS code's MFN/FTA base rate, ALL active chapter 99 rules (IEEPA/301/232 additional duties) matching the origin as verbatim text, and MPF/HMF fees. The LLM should walk the chapter-99 exception chains itself to stack the right duty layers, explain each step to the user, and always note this is an estimate. |
| watch_tariff_changesA | Saves HTS codes (with optional origin) to a local watchlist. After each dataset refresh, call check_tariff_updates to see whether the rates on these codes changed. This is how you track 2025-2026 tariff volatility without manual re-checking. |
| check_tariff_updatesD | Compares the current HTS snapshot with the previously fetched one. Call without codes to check the whole watchlist. Returns each change: code, column (general/special/other/additionalDuties), old → new value. |
| dataset_infoA | Fetch date, source, license, row counts — use to check data freshness. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: candidate search, detailed scenario calculation, watchlist management, update checking, and dataset metadata. Even the paired watch/check tools are unambiguous because one saves codes and the other compares snapshots.
Four tools follow a consistent verb_noun pattern: search_hs_candidates, calculate_tariff_scenario, watch_tariff_changes, check_tariff_updates. dataset_info breaks the pattern as a noun-only name, which is a minor deviation but not confusing.
Five tools is well-scoped for a focused tariff-resolution server. Each tool covers a distinct part of the workflow without redundancy or unnecessary breadth.
The core workflow is covered: search candidates, calculate duty scenarios, track changes, and verify data freshness. A minor gap is that watch_tariff_changes has no corresponding unwatch or list-watchlist tool, so watchlist management is slightly incomplete.