---
name: tariffs-jobs
description: "Step-by-step job recipes for the Tariff & HS Code Duty Finder MCP server: Find an HS code, HTS or customs code; Get customs duty, tariff and import tax. Use when the user asks things like \"What are candidate tariff codes for a lithium-ion battery imported into the US?\" or \"What is the UK import duty and VAT on commodity code 6914100000 from Vietnam?\""
license: MIT
---

# Tariff & HS Code Duty Finder jobs

Each section below walks through one job with the tools of the `tariffs` MCP server. The same recipes are MCP prompts (prompts/list) on `https://api.openkrill.app/gateway/mcp`.
Connect the server at `https://tariffs.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Find an HS code, HTS or customs code

Job: Find an HS code, HTS or customs code, with the Tariff & HS Code Duty Finder MCP server.

Use the `find_tariff_codes` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What are candidate tariff codes for a lithium-ion battery imported into the US?"

Steps:
1. Call `find_tariff_codes` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `description`, `country`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"description":"flower pot","country":"GB"}`
4. For the request "What are candidate tariff codes for a lithium-ion battery imported into the US?", a correct answer looks like this: Candidates led by 8507.60.00 (Lithium-ion batteries, 3.4%) with the heading above it, and a notice that they are candidates and not a binding classification.
5. Follow the server's own rules:
   - Use find_tariff_codes to turn a product description into candidate tariff codes and get_duty_rate to read the duty on a code.
   - Always send country: GB for goods imported into the United Kingdom, US for goods imported into the United States; ask which if the user did not say.
   - The codes are candidates, not a classification: say so every time, tell the user the right code depends on the product's make-up and use and that customs decides, and suggest confirming with customs or a licensed customs broker, or asking for a binding ruling, before declaring goods.
   - Describe the product plainly (what it is, the material, the use).
   - If nothing matches, retry with fewer or plainer words, or the product noun alone.
   - When several candidates fit, show the best few with their headings and let the user choose; do not pick one for them as the answer.
   - Pass on every note returned.
   - For the US, say that chapter 99 additional duties are not included.
   - Do not present the result as legal, customs or trade advice, and do not estimate total landed cost.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `find_tariff_codes`).

## Get customs duty, tariff and import tax

Job: Get customs duty, tariff and import tax, with the Tariff & HS Code Duty Finder MCP server.

Use the `get_duty_rate` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What is the UK import duty and VAT on commodity code 6914100000 from Vietnam?"

Steps:
1. Call `get_duty_rate` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `code`, `country`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"code":"6914100000","country":"GB","originCountry":"VN"}`
4. For the request "What is the UK import duty and VAT on commodity code 6914100000 from Vietnam?", a correct answer looks like this: Of porcelain or china: third-country duty 0.00%, VAT 20.00%, and the preferential rate for Vietnam (0.00%), with a note that a preferential rate needs proof of origin.
5. Follow the server's own rules:
   - Use find_tariff_codes to turn a product description into candidate tariff codes and get_duty_rate to read the duty on a code.
   - Always send country: GB for goods imported into the United Kingdom, US for goods imported into the United States; ask which if the user did not say.
   - The codes are candidates, not a classification: say so every time, tell the user the right code depends on the product's make-up and use and that customs decides, and suggest confirming with customs or a licensed customs broker, or asking for a binding ruling, before declaring goods.
   - Describe the product plainly (what it is, the material, the use).
   - If nothing matches, retry with fewer or plainer words, or the product noun alone.
   - When several candidates fit, show the best few with their headings and let the user choose; do not pick one for them as the answer.
   - Send originCountry (a two-letter code) to get_duty_rate when the user names where the goods come from, and read it as the schedule's rate for that origin, not as proof the goods qualify.
   - If get_duty_rate returns lines under the code instead of a rate, the code is not one goods are declared under: show the lines and ask which fits.
   - Pass on every note returned.
   - For the US, say that chapter 99 additional duties are not included.
   - Do not present the result as legal, customs or trade advice, and do not estimate total landed cost.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `get_duty_rate`).