Skip to main content
Glama

Compare US tariffs by origin

compare_origins
Read-onlyIdempotent

Compare US tariff layers for one HTS code across 2 to 6 countries of origin side by side, ranked by lowest total duty, to pick a sourcing origin.

Instructions

The US tariff layers of one HTS code from 2 to 6 countries of origin, side by side, lowest total first. Calls the Zentria Flow engine once per origin, 2 seconds apart, so it takes a few seconds. Duty only: freight, fees and supplier price are not compared. 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>",
      "origins": "<origins>"
    },
    "name": "compare_origins"
  }
}

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.
originsYes2 to 6 countries of origin (ISO-2 codes or English names), e.g. ["CN", "VN", "MX"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds behavior those annotations cannot express: one engine call per origin spaced 2 seconds apart, hence a multi-second latency, plus the caveat that results are a planning estimate rather than a customs ruling. It is silent on error handling for invalid origins, which keeps it below the top mark.

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?

Three tight sentences: what it compares and ordering first, then the latency expectation, then the accuracy caveat. No sentence repeats the name, title, or schema content unnecessarily, and nothing is buried at the end.

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?

Although no output schema exists, the description still discloses the ranking dimension ('lowest total first'), which is the key return-value property an agent needs. Combined with the latency note and the estimate-not-ruling caveat, nothing material is missing for a two-parameter read-only comparison 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 both hts and origins are already fully documented in the schema, including the 4-to-10-digit guidance and the ISO-2/English-name acceptance. The description only restates the 2-to-6 country range and adds no syntax or format detail beyond the schema, making the baseline 3 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 states a specific verb and resource ('The US tariff layers of one HTS code from 2 to 6 countries of origin, side by side, lowest total first') and pins the scope to duty only. The 'Duty only: freight, fees and supplier price are not compared' clause differentiates it from the landed_cost sibling without needing to name it.

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?

It gives clear usage context by bounding the comparison to duty and explicitly excluding freight, fees and supplier price, which signals when another tool (landed_cost) is the right choice. It never names that alternative outright, so the routing is implied rather than instructed.

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