Skip to main content
Glama

Search US tariffs

search_tariffs
Read-onlyIdempotent

Access: API key, OAuth, or x402 payment when offered. Search current US HTS classifications by product description, code, or prefix. Optionally include origin-specific rate stacks.

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_tariffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
countryNoCountry of origin: ISO-2 code (preferred). A country name, ISO-3 code or other casing is resolved to ISO-2 and disclosed in `normalized`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO-2 country code of origin"New value: +"Country of origin: ISO-2 code (preferred). A country name, ISO-3 code or other casing is resolved to ISO-2 and disclosed in `normalized`."
    • changedInput schema / properties / country / pattern
      Previous value: -"^[A-Za-z]{2}$"New value: +"^[A-Za-z][A-Za-z .,'\\u2019()-]{1,59}$"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely new context by disclosing alternate auth paths (API key, OAuth, x402 payment), but says nothing about result caps (limit max 25) or what a rate stack response contains.

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?

Three tight sentences with no filler, and the auth note is front-loaded where an agent will see it. Minor cost: the auth sentence precedes the purpose sentence, slightly delaying what the tool actually does.

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

Completeness3/5

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

For a 3-parameter read tool with no output schema, the description covers the main input mode and an optional enrichment, which is close to adequate. Gaps remain around result volume (the 1–25 limit), pagination/truncation behavior, and what 'rate stacks' contain.

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 only 33% — only `country` is documented, and the description compensates for `query` by specifying accepted input forms (description, code, prefix). It also links `country` to origin-specific rate stacks, but `limit` gets no treatment beyond its schema bounds, so compensation is partial.

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?

Names a specific verb (Search) and resource (current US HTS classifications), and enumerates the three query modes: product description, code, or prefix. It does not explicitly distinguish itself from lookup_tariff or search_rulings, so it falls just short of 5.

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 query modes imply this is the broad/fuzzy search entry point, and 'optionally include origin-specific rate stacks' sketches an optional branch. However, no sibling is named and there is no statement of when to prefer lookup_tariff or compare_tariff_codes over this, leaving selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources