within

What an item costs delivered

delivered_price

Read-onlyIdempotent

Calculate the landed cost of one item shipped to a country by adding its price, boutique delivery, and estimated duties, tariffs, taxes, and fees. See the total cost at the door before buying.

Instructions

What one item on within costs delivered to a country: the item's price, the boutique's own delivery price, and an estimate of the duty, tariffs, tax and fees, added up to the landed cost at the door. The duty estimate covers the United States, the United Kingdom and Australia; Canada adds sales tax by province; for other countries it gives the item and delivery only and says what is missing. Use this when someone asks what an item really costs shipped to them, for the total with shipping and customs, or for an import duty, customs duty or landed cost calculator on one item. Name the item by its shopwithin.co link, or by boutique_domain and id. The url is a shopwithin.co product page link; the tool reads within's own catalog, documented at https://shopwithin.co/agents. 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": {
      "country": "<country>"
    },
    "name": "delivered_price"
  }
}

Input Schema

Name	Required	Description
`id`	No	The item's id from a result, with boutique_domain.
`url`	No	The item's shopwithin.co link, e.g. https://shopwithin.co/product/<boutique>/<words>/<id>.
`kind`	No	What the item is, for the duty rate, when the answer says it is missing. 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.
`region`	No	The province or state: a Canadian province by name or code ('ON', 'Quebec'), a US state by its two letter code ('NY'). Canada needs it for sales tax; some delivery prices differ by province or state.
`country`	Yes	Where it is delivered: a country name or two letter code, e.g. 'US', 'Canada', 'United Kingdom'.
`made_in`	No	Where the item was made, as a country name or two letter code (e.g. 'IT'), when the answer says it is missing. It is on the item's label or in its description.
`boutique_domain`	No	The item's boutique_domain from a result, with id.

Output Schema

Name	Required	Description	Default
`duty`	Yes
`item`	Yes
`note`	Yes
`found`	Yes
`price`	Yes
`ships`	Yes
`total`	Yes
`country`	Yes
`missing`	Yes
`delivery`	Yes
`sales_tax`	Yes
`estimate_note`	Yes

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?

Beyond the read-only and idempotent annotations, the description discloses the country coverage matrix (US/UK/AU duty estimates, Canada provincial sales tax, other countries returning item and delivery only plus what is missing). It also sets accuracy expectations ('It is an estimate; the carrier's bill is the final word') and documents the data source with a reference URL. This is exactly the context annotations cannot convey.

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?

A single dense paragraph that front-loads the definition, then usage, then item identification, then the estimate caveat. It is appropriately sized for a seven-parameter multi-country calculator, though phrases like 'duty, tariffs, tax and fees' and the slightly awkward 'on within' opening add mild redundancy and friction.

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?

For a tool with an output schema, the description covers what the structured fields cannot: country-specific behavior, graceful degradation for unsupported countries, the iterative kind/made_in fill-in, and the estimate-not-quote caveat. Nothing an agent needs to select and correctly invoke this tool appears to be missing.

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 the identification rule the schema only hints at: name the item by its shopwithin.co link, or by boutique_domain and id. It also explains the recovery flow in which kind and made_in are supplied after a result says they are missing, which is not evident from the field descriptions alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific computation and its components: item price, boutique delivery price, and an estimate of duty, tariffs, tax and fees summed to a landed cost. An agent can distinguish it from a plain price lookup or a duty-only tool from the text alone. It stops short of naming sibling tools like estimate_duty or price_check, so differentiation is implied rather than explicit.

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 concrete trigger phrasings ('what an item really costs shipped to them', 'total with shipping and customs', 'import duty, customs duty or landed cost calculator on one item'), which is clear when-to-use guidance. It also delimits scope behaviorally by listing which countries get full duty estimates versus partial results. There are no explicit when-not conditions or named alternative tools, which keeps it below a 5.

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