within

Estimate import duty and tax

estimate_duty

Read-onlyIdempotent

Calculate import duty, taxes, tariffs, and carrier fees for clothing, shoes, bags, jewellery, watches, or accessories shipped to the US, Canada, UK, or Australia.

Instructions

Work out what clothing, shoes, a bag, jewellery, a watch or an accessory costs at the door when it is shipped to the US, Canada, the UK or Australia: the duty, any extra tariff on the country it was made in, the tax, the government and carrier fees, and the total. Every line names its official source and the day it was read, and the answer links the page on shopwithin.co/duty-calculator that shows it. Use this when someone asks about customs, duty, tariffs or import tax on an order from another country, or wants an import duty calculator. It is an estimate; the carrier's bill is the final word.

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": {
      "to": "<to>",
      "price": "<price>",
      "currency": "<currency>",
      "kind": "<kind>",
      "made_in": "<made_in>",
      "ships_from": "<ships_from>"
    },
    "name": "estimate_duty"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Where the piece is shipped to.
`kind`	Yes	What the piece is, one of: coat-wool, coat-cotton, coat-polyester, puffer-down, jacket-wool, jacket-cotton, jacket-polyester, jacket-leather, blazer-wool, blazer-cotton, blazer-polyester, trousers-wool, trousers-cotton, trousers-polyester, dress-wool, dress-cotton, dress-silk, dress-polyester, skirt-wool, skirt-cotton, skirt-polyester, shirt-cotton, shirt-silk, shirt-polyester, tshirt-cotton, tshirt-polyester, sweater-cashmere, sweater-wool, sweater-cotton, sweater-polyester, shoes-leather, sneakers-leather, boots-leather, sneakers-textile, bag-leather, bag-textile, wallet-leather, jewellery-gold, jewellery-silver, jewellery-costume, watch-automatic, watch-gold, belt-leather, scarf-silk, scarf-wool, tie-silk, sunglasses.
`price`	Yes	The price, without shipping.
`usmca`	No	US only: true if a piece made in Canada or Mexico qualifies under USMCA.
`region`	No	Canada only: the province code, e.g. ON, QC, BC.
`made_in`	Yes	Two letter country code of where it was made, e.g. IT, FR, CA, US, JP.
`ship_by`	No	us: fedex, courier or post. canada: fedex, courier or post. uk: royalmail, parcelforce or courier. australia: courier or post.
`currency`	Yes	The currency of the price.
`shipping`	No	Optional shipping cost, in the price's currency.
`weight_kg`	No	Optional weight; a few US lines add a charge per kilogram.
`department`	No	Women's or men's; some duty rates differ.
`ships_from`	Yes	Two letter country code of where it ships from.

Output Schema

Name	Required	Description	Default
`to`	No
`note`	No
`page`	No
`found`	No
`lines`	No
`notes`	No
`total`	No
`value`	No
`status`	No
`currency`	No
`estimate_note`	No
`tax_at_checkout`	No
`what_changes_it`	No
`exchange_rate_date`	No
`owed_before_delivery`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare a safe, closed-world, idempotent read, so the bar is low, yet the description still adds the things an agent needs: each line carries its official source and read date, the response links the corresponding shopwithin.co/duty-calculator page, and the result is explicitly an estimate with the carrier's bill as final authority.

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 computation and its components, then the usage trigger, then the accuracy caveat — a sensible order with no filler. The opening sentence is long and enumerative, but every element in it is meaningful.

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 12-parameter tool with an output schema and full annotations, the description covers scope, when to use it, provenance of figures and the estimate caveat. Optional-vs-required and jurisdiction-specific parameters are left to the schema, which is acceptable given coverage is complete.

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 every parameter is already documented. The description only echoes that origin country drives an extra tariff and that destinations are limited to four countries; it adds nothing about usmca, region, ship_by, weight_kg or the long kind enum, so the baseline of 3 applies.

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?

Names a specific computation (duty, country-of-origin tariff, tax, government and carrier fees, total) over concrete categories (clothing, shoes, bags, jewellery, watches, accessories) and named destinations (US, Canada, UK, Australia). An agent can tell exactly what the tool returns without opening the schema.

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?

Gives explicit trigger conditions: someone asking about customs, duty, tariffs or import tax on a cross-border order, or wanting an import duty calculator. It stops short of naming alternatives such as delivered_price or price_check, so an agent isn't told which sibling to prefer when the question is just about landed cost.

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