Skip to main content
Glama

Zentria Flow

Compare US tariffs by origin

compare_origins
Read-onlyIdempotent

The US tariff layers of one HTS code from 2 to 6 countries of origin, side by side, lowest total first. 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 observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds real substance: it is duty-only (freight, fees and supplier price excluded), results are ranked lowest total first, and it is a planning estimate rather than a customs ruling. That last caveat is a behavioral constraint the annotations cannot express.

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 short sentences, front-loaded with what the tool produces and its ordering, followed by scope exclusions and the disclaimer. No filler and nothing repeated from the title.

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 two-parameter read-only comparison with no output schema, the definition covers the essential scope, exclusions and result ordering. The return shape (per-origin duty breakdown plus total) is only hinted at via 'tariff layers' and 'side by side', which is a minor remaining gap.

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%, so both parameters (HTS code and origin list) are fully documented in structured data, including length bounds and the estimate-vs-priced distinction for shorter codes. The description only restates the 2-to-6 origin range, adding no format or syntax detail beyond the schema.

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 gives a specific verb and resource — it layers US tariffs for one HTS code across 2 to 6 origins 'side by side' — and adds the ordering rule ('lowest total first'). The multi-origin comparative framing is enough to distinguish it from a single-code tariff lookup or an HTS search without opening a schema.

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?

Usage is implied rather than stated: comparing origin options for one code. There is no explicit 'use this when...' clause and no named alternative among the sibling tools, though the scope wording ('one HTS code', '2 to 6 countries') narrows applicability.

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.