Skip to main content
Glama
Sign In

trimtab-ais

by io.github.mrsingh86
OverviewDiscussionsAdmin

US tariff rulebook + receipts, per HS code

tariff_lookup
Read-only

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.

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": {
      "hs": "<hs>"
    },
    "name": "tariff_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
hsYesHS code, 2 to 10 digits (dots optional), e.g. 9401.61 or 847130
originNoOrigin country name (e.g. China, Vietnam) — adds in-force measures and receipts reality (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavioral traits: measures are matched by origin/sector not by code, many are product-specific and do not apply, and users are instructed to quote the 'answer'/receipts_reality rather than add up addon_pct. This adds substantial context for safe usage.

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

Conciseness5/5

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

The description is dense yet every sentence serves a purpose: it front-loads the imperative 'CALL THIS', explains return structure, warns about sector matching, gives an example, and notes no API key required. It is well-organized for an agent to parse quickly.

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?

With no output schema, the description carries the full burden of explaining return values. It enumerates the answer line, statutory MFN base, Chapter-99 provisions with Federal Register citations, and receipts_reality. It also includes caveats about product-specific measures and non-applicability, making it complete for practical use.

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?

The schema already covers hs and origin well (100% coverage), but the description enriches meaning by stating that origin adds in-force measures and receipts reality, and by contextualizing how hs is used (the schedule behind one HS code). It does not fully explain hs format expectations beyond the schema, so a 4 is appropriate.

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 uses a specific verb ('CALL THIS') and resource ('US tariff rulebook + receipts, per HS code'), and immediately distinguishes the tool from siblings by noting 'For "what does X from Y pay" prefer tariff_story.' This makes the purpose unmistakable.

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?

The description explicitly states when to use this tool ('for the schedule behind one HS code'), when not to ('do not recite it from memory'), and names an alternative (tariff_story). It also warns against misusing sector-specific measures, providing clear usage boundaries.

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

All trimtab-ais toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources