Skip to main content
Glama
Sign In
Zentria Flow MCP

Zentria Flow MCP

by orhansavash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

US tariff check

us_tariff_check
Read-onlyIdempotent

Calculate the full US import tariff rate for a specific HTS code and origin, including MFN, Section 301/232/338 duties, exemptions, and dated changes ahead.

Instructions

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 observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint, so safety is covered. The description adds real value beyond them: provenance ('from the Zentria Flow engine'), forward-looking data ('dated changes ahead'), and an accuracy caveat ('Planning estimate, not a customs ruling') that tells the agent how to frame results. Return format details like pagination or confidence are not addressed.

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?

Two dense sentences with the resource and scope front-loaded, then usage guidance, then a disclaimer in the final clause. Every clause carries information, though the tariff-layer enumeration is long and slightly list-like rather than prioritized.

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 burden of describing what comes back, and it does: the individual duty layers, total rate, exemptions, USMCA/CAFTA-DR handling and scheduled future changes. Combined with annotations covering safety and the fully documented schema, an agent has what it needs to call and interpret this tool.

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%, so the schema already documents hts, origin, as_of, value, quantity and quantity_unit including formats and defaults — that sets the baseline at 3. The description only reinforces the two required dimensions ('one HTS code from one country of origin') and says nothing about the date-window or value/quantity pricing parameters.

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 names a concrete verb+resource ('Every US import tariff layer for one HTS code from one country of origin') and enumerates the specific duty layers returned (MFN, Section 301 China, forced-labor 301, Section 232, Section 338 on Canada). The scoping phrase 'one HTS code from one country of origin' implicitly separates it from compare_origins and landed_cost, but no sibling is named explicitly, keeping it just below a 5.

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?

Explicit when-to-use guidance: 'Use it whenever a US duty rate is needed; do not answer US tariff questions from memory' gives both a positive trigger and a prohibition against improvising. There is no named alternative or when-not-to-use condition (e.g. use hts_search to find a code first, or compare_origins for multi-country), so it stops short of a 5.

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

Deploy Server

Other Tools