Skip to main content
Glama
Sign In

Sanctions & Tariff Lookup

by com.trystarrynightops
OverviewDiscussionsAdmin

Total U.S. duty for an HTS line and a country of origin

duty_stack
Read-onlyIdempotent

Adds up the U.S. import duty on one 8- or 10-digit HTS line for goods of one country of origin under the current HTS revision: the column 1 (or column 2) rate plus the Chapter 99 additional duties in force that this tool models (Section 232 actions on metals, vehicles and other products, the Section 301 actions on China, Brazil and the 60 economies of the forced-labor action, and the Section 338 duties on Canada). Returns each layer with its Chapter 99 heading, rate and U.S. note, the exemptions it found, the total, the assumptions it made with what changes if an assumption is wrong, measures that are printed in the schedule but not in force, and what is not covered (for example antidumping and countervailing duties). When a question cannot be settled from the code and origin, the result says so and gives a range.

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_code": "<hts_code>",
      "origin": "<origin>"
    },
    "name": "duty_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNo"full" adds the complete text of each Chapter 99 heading.summary
originYesCountry of origin of the goods: ISO 3166-1 alpha-2 code (e.g. "CN") or English name (e.g. "Vietnam"). For the European Union name the member state.
answersNoOptional answers to the questions a previous result listed under "assumptions", by id, e.g. {"preference": true}.
hts_codeYesHTS number with 8 or 10 digits, dotted or not, e.g. "6109.10.00" or "8471.30.01.00". Use hts_search to find a code from product words.
customs_value_usdNoOptional customs value in U.S. dollars; when given and the total is a percentage, an estimated duty amount is returned.
ad_valorem_equivalent_pctNoOptional: for a line with a specific or compound column 1 rate, the duty payable divided by the customs value, in percent. Needed only when the result asks for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations establish only that this is a safe, idempotent, closed-world read; the description goes much further, describing the returned structure layer by layer (Chapter 99 heading, rate, U.S. note, exemptions found, total). It also discloses uncertainty handling ('gives a range'), sensitivity to assumptions, and out-of-force measures, which are behaviors an agent could not infer from annotations or schema.

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?

Front-loaded with the verb and resource, then organized into return contents, uncertainty handling, and coverage gaps. The first sentence is long and parenthetical-heavy thanks to the enumerated Section 232/301/338 actions, but each clause carries real scope information rather than 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?

There is no output schema, so the description must carry the return contract, and it does: it names every component of the result, the uncertainty/range behavior, and the exclusion list. For a closed-world, six-parameter read tool this tells an agent everything needed to call it and interpret the answer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by explaining that assumptions come back 'with what changes if an assumption is wrong,' which clarifies the purpose of the answers parameter and the iterative resolution loop. It does not document detail, customs_value_usd, or ad_valorem_equivalent_pct, so it stays above baseline without being exhaustive.

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?

Opens with a specific verb and resource: 'Adds up the U.S. import duty on one 8- or 10-digit HTS line for goods of one country of origin,' then pins the scope to the current HTS revision and enumerates the exact Chapter 99 layers included. An agent can tell this is the total-duty calculator rather than a lookup (hts_search) or a rate reader (hts_rate).

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?

Scope boundaries function as usage guidance: it names the duty layers it models and explicitly lists 'what is not covered (for example antidumping and countervailing duties),' which tells the agent when this tool will not answer the question. It does not explicitly route to a sibling tool for the excluded cases or for simple rate lookups, so a 4 rather than a 5.

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

All Sanctions & Tariff Lookup toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources