Fromerica U.S. Trade Data

Search U.S. import tariffs (HTS)

search_us_tariffs

Read-only

Search the official U.S. Harmonized Tariff Schedule (USITC, refreshed daily) by product words or by an HTS code prefix. Returns up to 20 tariff lines with their general, special and column 2 duty rates and a link to each code's page on Fromerica.

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": {
      "query": "<query>"
    },
    "name": "search_us_tariffs"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Product words (e.g. "solar panels") or an HTS code prefix (e.g. "8541" or "9903.88").

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the bar is lower, and the description still adds real context: the upstream source (USITC), daily refresh, the 20-line result cap, and that each hit carries general/special/Column 2 rates plus a per-code link. It doesn't clarify rate-date applicability or what happens when a prefix spans thousands of lines.

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?

Two sentences, front-loaded with the verb and resource, then the return shape. No filler or redundant restatement of the tool name.

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

Completeness4/5

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

For a one-parameter, no-output-schema tool, the description covers source, refresh cadence, result cap, and return contents well enough to call it correctly. Only minor gaps remain (exact-code alternative, truncation/refinement guidance when 20 lines are hit).

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% and the single 'query' parameter is already documented with examples in the schema; the description's 'product words or HTS code prefix' restates that. No additional format rules (e.g., minimum prefix length, matching behavior) are contributed beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb (search) plus resource (U.S. Harmonized Tariff Schedule) and two supported query modes. It implicitly separates itself from the exact-code sibling get_us_tariff by framing this as a prefix/word search capped at 20 lines, though it never names that sibling outright.

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

Usage Guidelines3/5

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

The description tells the agent what inputs work (words vs. code prefix), which implies when the tool fits, but it never states when to prefer the sibling get_us_tariff for an exact code or what to do with zero results. Usage is inferable rather than stated.

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

All Fromerica U.S. Trade Data tools Inspect

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

Need Help?