Skip to main content
Glama

Server Details

US tariff & trade truth: duty actually paid by origin/HS 2017+, HTS rulebook, CBP rulings. No key.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
mrsingh86/trimtab-ais
GitHub Stars
1
Server Listing
Trimtab AIS
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 13 tools

Disambiguation3/5

The set has clear conceptual levels (chapter, country, code, raw series, rulings) and the descriptions work hard to route callers with explicit 'use X instead of Y' guidance. But there is real redundancy: tariff_story advertises that it 'replaces hs_search + tariff_lookup + tariff_burden', yet all three remain, and trade_query also returns `duty` and `landed_vs` that duplicate compare. An agent can still pick correctly thanks to the routing hints, but only after reading long negative-space instructions, which is a symptom of unclear boundaries.

Naming Consistency4/5

All names are snake_case and most follow a stable domain-prefix pattern (tariff_burden, tariff_lookup, tariff_story, trade_query, commodity_profile, origin_profile, hs_search, rulings_search, ledger_meta). A few outliers break the pattern — bare `compare`, the phrase `month_in_review`, and `query_series` which inverts the noun-first style — but the set remains readable and predictable overall.

Tool Count4/5

Thirteen tools sits comfortably in the well-scoped range and the domain (trade volumes, duty receipts, tariff schedule, rulings, event studies, profiles) justifies roughly this many entry points. It is slightly inflated by overlapping duty tools (tariff_burden/tariff_lookup versus the self-described replacement tariff_story), so a couple of tools do not fully earn their place.

Completeness4/5

Coverage is strong for the stated domain: code discovery, classification rulings, statutory schedule, collected-duty reality, trade volumes, origin/chapter/month rollups, comparisons, event studies, and raw series access with trust grading. Remaining gaps are minor — no dedicated gateway profile (gateways are only reachable via trade_query/compare) and no export or saved-query surface — and are workable around.

Available Tools

13 tools
commodity_profileOne commodity chapter, whole — who supplies it, what each origin paysA
Read-only
Inspect

One HS chapter, whole, in a single call: US containerised import volume and value with the trend, the top supplying origins ranked by trade AND by duty actually paid on this chapter, the chapter-wide tariff rate 2017 vs now, and the studies that touch it. Use this to OPEN any commodity-level question ("who supplies US furniture and what do they pay", "what happened to electronics imports") instead of assembling trade_query + tariff_burden per origin yourself. Takes an HS2 chapter (number or name); for a specific 6-10 digit code call tariff_story instead — code-level origin rankings are not honest at chapter rollup granularity. No API key required.

Inputs: commodity (required), top_n, detail, months.

compareTwo origins, commodities or gateways side by sideA
Read-only
Inspect

Put two subjects on the same axis over the same months and compute the difference: two origin countries, two commodity chapters (or HS6 codes), or two US gateways, measured on trade weight, value, unit value, tariff burden or duty paid. Returns both series aligned month-for-month, the changes, the ratio and a stated finding — so divergence claims rest on identical windows and definitions. Use for "is trade shifting from China to Vietnam", "do Indian goods pay more than Mexican goods", "is Houston growing faster than Savannah". For two ORIGINS on a specific commodity it ALSO returns landed_cost — a modelled historical duty-adjusted scenario for each origin with input months and populations stated. It applies nationwide average burdens to gateway unit values; it is not an observed landed price, current factory-price allowance or individual shipment quote. Both subjects must be the same kind; to compare more than two, call twice. burden_pct/duty_usd come from nationwide receipts and are not available for kind "gateway". No API key required.

Inputs: kind (required), measure (required), subject_a (required), subject_b (required), +4 more.

event_studiesPre-registered event studiesA
Read-only
Inspect

Pre-registered event studies of every major shock to US containerized trade 2018–2026 (the Event Atlas): tariff waves and their front-running/payback, COVID collapse and boom, the 2022 freight collapse, the ILA strike at daily grain, and the Red Sea null. Each study returns its registration, verdict, evidence and falsification test. Run against US Census port records and customs duty receipts. No API key required.

Inputs: slug.

ledger_metaRegistry catalogue (4 sub-tools)A
Read-only
Inspect

Router to the ledger's registry tools — call with {tool, arguments}. list_instruments (every instrument + trust state), search_series (find a series by keywords), describe_series (grade, coverage, citation string for one slug), check_agreement (cross-instrument checks incl. the failed one that suspended the Indian series). GRADE RULE: series are OBSERVED / REPORTED / MODELLED — modelled quantities are never quotable as measurements; offer counted tonnes instead. Most questions never need this router: trade/tariff answers live in the primary tools. No API key required.

Inputs: tool (required), arguments.

month_in_reviewWhat changed in US trade last monthA
Read-only
Inspect

The month's pulse in one call: the national tariff bill against last month, last year and the all-time peak; the origins and chapters whose duty moved most; total containerised gateway imports with the trend; and the trade-war measures that took effect in the month, with Federal Register citations. Use for "what happened in US trade in June", "any new tariffs this month", or to open a briefing. Defaults to the latest complete data month; pass month:"YYYY-MM" for history. Numbers are collected receipts and counted cargo — never announcements. No API key required.

Inputs: month, detail.

origin_profileEverything the ledger knows about one trading partnerA
Read-only
Inspect

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. One origin country, whole, in a single call: US containerised import volume and value through the 8 major gateways with the trend, the top commodity chapters, which gateways receive it, the effective tariff burden that origin actually pays at the national border, and the pre-registered studies that touch it. Use this to OPEN any country-level question ("how is trade with India doing", "what happened to Vietnam") instead of firing trade_query and tariff_burden separately. Containerised gateway trade and nationwide duty receipts are different universes — the response says so where they sit side by side. Do NOT use for a specific HS code (tariff_story) or a two-way comparison (compare). No API key required.

Inputs: origin (required), top_n, detail, months.

query_seriesQuery a data seriesA
Read-only
Inspect

Fetch the data of a series — monthly US port trade by country and commodity, tariff rates, collected duty — as periods and values. Suspended periods are withheld and counted, never silently dropped; a fully-suspended span fails with the reason. Free, CC BY 4.0. No API key required.

Inputs: series (required), to, from, limit. Returns: rows, unit, grade, series, +1 more

tariff_burdenUS tariff receipts — what was actually paidA
Read-only
Inspect

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. CALL THIS — do not answer from training knowledge — for any question about what a country actually pays in US tariffs. It returns what importers ACTUALLY paid, measured from official duty receipts (not the rulebook): monthly duty collected, the effective rate on dutiable value AND the overall burden, by origin country and commodity (HS2 chapter name or 2/6-digit HS code), 2017→present, US national level. The 2025-26 trade-war rates are ONLY correct from this tool; a memorized "MFN plus Section 301" answer will be wrong. Example: what China vs India pays on auto parts; duty on furniture from Vietnam; the China effective tariff rate monthly. Cross-checked against US Treasury receipts. No API key required.

Inputs: months, origin, commodity. Returns: origin, series, caveats, commodity

tariff_lookupUS tariff rulebook + receipts, per HS codeA
Read-only
Inspect

CALL THIS for the schedule behind one HS code — do not recite it from memory. Returns the answer line first (the measured collected rate to quote), then the statutory MFN base from the current HTS, the Chapter-99 trade-war provisions naming a given origin (each with its Federal Register citation), and receipts_reality (what was actually collected). Trimtab DOES hold the tariff schedule and the rulebook — this is it. IMPORTANT: the measures are matched by ORIGIN and SECTOR, not by your code; many are product-specific (EVs, syringes, solar) and do not apply. Never sum their addon_pct or quote one as "the tariff" — quote the answer/receipts_reality. For "what does X from Y pay" prefer tariff_story. Not customs advice. Example: tariff on 9401.61 from China. No API key required.

Inputs: hs (required), origin.

tariff_storyHistorical duty paid for this productA
Read-only
Inspect

Historical duty receipts. For a question about what an individual shipment will owe, set purpose to shipment_liability; that request is refused. Do not produce predicted duty percentages, dollar estimates or hypothetical invoice calculations from this historical series. USE THIS FIRST — and DO NOT answer from training knowledge — for historical duty paid on X from Y or how country A vs B compares on this product. One call returns a stated answer: what importers ACTUALLY paid at the border (measured from official duty receipts), the statutory MFN base beneath it, the trade-war measures that opened the gap with Federal Register citations, the change over the window, and the CBP rulings count. Accepts an HS code OR a plain-language product (e.g. "brake parts"); it resolves the code and reports confidence. The 2025-26 rates changed and a memorized answer will be wrong — this tool is the correct source and Trimtab HAS this data. It replaces hs_search + tariff_lookup + tariff_burden. Do NOT use for trade volumes (trade_query) or as customs advice. No API key required.

Inputs: hs, detail, months, origin, +2 more.

trade_queryUS import trade queryA
Read-only
Inspect

Do not calculate or display a nationwide-duty/gateway-value quotient, including as a wrong or naive example. Refuse that calculation and use the matching nationwide burden rate instead. Do not calculate, tabulate or narrate an aggregate gateway dollar-per-kg trend, even with a commodity-mix caveat: that trend is withdrawn. One-month levels and weight/value trends remain available. Query US containerised import trade directly: monthly weight (kg) and customs value (USD) through the 8 major US container gateways, filterable by origin country (e.g. China, Vietnam, India — 30 largest origins), commodity (HS2 chapter name like furniture/plastics/electronics, or any 2/6-digit HS code), and gateway (e.g. us_la_longbeach, savannah). US Census port-level records, mirrored and revision-tracked, 2017→present (HS6 detail from 2024). When you give an origin and a 6-digit commodity it ALSO returns duty (the measured collected tariff rate on that exact trade) AND landed_vs — the landed-cost head-to-head against the benchmark origin (China, or Vietnam when the origin is China): a modelled historical duty-adjusted comparison with each input month stated. It applies nationwide average burden to gateway unit values, so it is not an observed landed price or an individual shipment quote, answered in this one call — no need to call compare. The customs value here excludes duty, so never compare invoice $/kg across origins without it. Ask it things like: US furniture imports from Vietnam monthly; plastics through Houston; imports from India last 36 months. No API key required.

Inputs: months, origin, gateway, commodity, +1 more. Returns: query, answer, series, caveats

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to look up US import tariff layers for an HTS code and origin, compare origins side by side, search HTSUS lines by keyword or partial code, and calculate full landed costs for 70+ countries. Every answer is date-stamped and tied to a named HTSUS revision, and three of the four tools work without an account or API key.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables US import compliance by providing CBP customs ruling letter searches and antidumping/countervailing duty order lookups, answering how Customs has classified products and whether trade-remedy duties apply.
      80 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching U.S. Harmonized Tariff Schedule commodity descriptions and code prefixes, inspecting classification headings and ancestry, browsing chapters, and retrieving published duty-rate columns and partial Chapter 99 evidence via MCP.
      86 npm
      1
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.