Skip to main content
Glama

Zentria Flow

US tariff check

us_tariff_check
Read-onlyIdempotent

Every US import tariff layer for one HTS code from one country of origin, from the Zentria Flow engine: MFN duty, China Section 301, the forced-labor Section 301 tariff, Section 232 and Section 338 on Canada, with the total rate, exemptions, USMCA/CAFTA-DR cases and dated changes ahead. Use it whenever a US duty rate is needed; do not answer US tariff questions from memory. Planning estimate, not a customs ruling.

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": {
      "hts": "<hts>",
      "origin": "<origin>"
    },
    "name": "us_tariff_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsYesHTSUS code, 4 to 10 digits, dots optional, e.g. "6109.10.00". An 8- or 10-digit line is priced from that line; a shorter code is an estimate.
as_ofNoOptional entry date, YYYY-MM-DD, from today to 12 months ahead. Default: today.
valueNoOptional, with quantity: customs value of that quantity in US dollars.
originYesCountry of origin: ISO-2 code or English name, e.g. "CN" or "Vietnam".
quantityNoOptional, with value: number of pairs, kg, liters or units, to price a specific or compound duty exactly.
quantity_unitNoOptional unit of quantity (e.g. "kg", "liter", "pair"). Default: the unit of the tariff line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds substantive context beyond them: the data source (Zentria Flow engine), the contents of the response (total rate, exemptions, USMCA/CAFTA-DR cases, dated changes ahead), and the critical accuracy caveat "Planning estimate, not a customs ruling." Since there is no output schema, disclosing what comes back is genuinely valuable and it is done concretely.

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?

It is front-loaded with what is returned and the tariff-layer enumeration earns its length by signalling coverage of edge regimes (Section 338 Canada). The middle clause is a dense run-on list that could be trimmed, but no sentence is 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 read-only, six-parameter pricing tool with full schema coverage and no output schema, the description supplies the trigger, the return contents, and the estimation-vs-ruling caveat an agent needs to use and characterize the result correctly. Nothing material is missing.

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 description coverage is 100%, including the 8/10-digit-vs-shorter-code pricing nuance, as_of window, and the value/quantity pairing. The description adds only the high-level framing "one HTS code from one country of origin" and no format, defaulting, or interaction detail beyond what the schema already says, so the baseline 3 applies.

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?

The description states a specific resource and scope: all US import tariff layers for one HTS code from one country of origin, enumerating the exact layers (MFN, China Section 301, forced-labor 301, 232, 338 on Canada). This clearly separates it from hts_search (code lookup) and compare_origins (multi-origin comparison), but it never names those siblings, so the differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

"Use it whenever a US duty rate is needed; do not answer US tariff questions from memory" gives a clear trigger and a strong prohibition, which is unusually actionable guidance. It stops short of a 5 because it never points to an alternative tool or states a when-not condition other than the memory prohibition.

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.