Skip to main content
Glama

us-tariff-ledger

by com.trimtabist

What it costs to import this, and what changed

tariff_story
Read-only

USE THIS FIRST — and DO NOT answer from training knowledge — for ANY "what is the tariff on X from Y" or "how does country A vs B compare on this product" question. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hsNoHS/HTS code, 2-10 digits, dots optional (e.g. 9401.61). Provide this OR product.
detailNoanswer = headline + citation (~250 tokens). standard = + measures, history, rulings (~900). full = + the complete monthly series.standard
monthsNoPaid-rate history window, trailing months.
originNoOrigin country (China, Vietnam, "Korea", "UK"...). Omit for all origins — much weaker, overlays are origin-specific.
productNoPlain-language product, 1-3 words ("standing desk"). Provide this OR hs.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark readOnly=true and destructive=false, but the description adds critical behavior: data comes from official duty receipts, resolves HS codes and reports confidence, includes a warning that 2025-26 rates changed, and notes no API key required. This goes well beyond the annotations.

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?

The description is longer than average but front-loaded with the imperative 'USE THIS FIRST' and each sentence adds substantive guidance. The phrase 'Trimtab HAS this data' is slightly promotional but reinforces reliability. No wasted filler.

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?

For a tool with no output schema, this description is remarkably complete: it covers purpose, data sources, output components, exclusions, alternatives, prerequisites (none), and operating conditions. An AI agent would know exactly when and how to invoke this tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the hs/product 'OR' relationship and the confidence reporting on resolution, which is not in the schema. However, most parameter semantics are already in the schema descriptions.

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?

The description opens with 'USE THIS FIRST' and explicitly states it answers 'what is the tariff on X from Y' or comparison questions, listing the exact outputs (actual paid rates, MFN base, trade-war measures, change, rulings). It distinguishes from siblings by declaring 'It replaces hs_search + tariff_lookup + tariff_burden.'

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('for ANY...') and when-not-to-use ('Do NOT use for trade volumes (trade_query) or as customs advice'). Names the alternative tool for trade volumes and orders usage with 'USE THIS FIRST'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All us-tariff-ledger toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation3/5

Tariff-related tools (tariff_story, tariff_burden, tariff_lookup, trade_query) overlap in scope, with tariff_story explicitly replacing three others, which creates confusion. However, each has a distinct granularity and the detailed descriptions help an agent choose correctly most of the time.

Naming Consistency3/5

All tools use lowercase snake_case, but the structure is inconsistent: some are noun phrases (commodity_profile, origin_profile), some verb-first (compare, query_series), and some noun-verb combinations (hs_search, rulings_search). This mix, while readable, lacks a unifying pattern.

Tool Count5/5

13 tools is appropriate for a comprehensive trade/tariff data server; each covers a distinct aspect without bloating the surface.

Completeness5/5

The tool set covers HS code search, tariff lookup, actual duty paid, trade volumes, country and commodity profiles, comparisons, event studies, monthly summaries, CBP rulings, and raw series queries—leaving no major gaps for the stated domain.

Resources