出口单 chukoudan

关税估算

duty-estimate

Read-onlyIdempotent

关税估算（Duty estimator）：这批货运到英国，买家要付多少关税和增值税，到岸总成本是多少。 What duty and VAT the buyer pays on a consignment to the UK, and the landed cost. 读取数据 / Reads: duty-rules@current, uk-tariff@current. 输入为精确的十进制字符串 / Inputs are exact decimal strings. 用户没有给的数字和日期不要自己编：必填的先问用户，选填的不填。 / Never make up a figure or a date the user did not give: ask for a required one, leave an optional one out. 回复时引用回答里的 provenance.source_line / Quote provenance.source_line in your reply. 结果仅供计算参考，不是税务、法律或投资意见；回答时请带上返回的说明和来源行。 / The result is for calculation and reference only, not tax, legal or investment advice; when you answer, pass on the returned notice and source line.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rate": "0.75",
      "goods": "5000",
      "freight": "600",
      "vatRate": "20",
      "currency": "USD",
      "dutyRate": "2",
      "quantity": "1000",
      "insurance": "30",
      "destination": "gb"
    },
    "name": "duty-estimate"
  }
}

Input Schema

Name	Required	Description
`rate`	No	汇率（1 单位币种折多少英镑） / Exchange rate (pounds for 1 unit of the currency)
`goods`	Yes	货值（整批货的总价） / Goods value (whole consignment)
`freight`	No	运费（选填） / Freight (optional)
`vatRate`	Yes	增值税 VAT 税率 (%) / VAT rate (%)
`currency`	Yes	币种 / Currency
`dutyRate`	No	关税税率 (%) / Duty rate (%)
`quantity`	No	数量（选填） / Quantity (optional)
`insurance`	No	保险费（选填） / Insurance (optional)
`destination`	Yes	目的国 / Destination

Output Schema

Name	Required	Description	Default
`tool`	Yes
`links`	Yes
`steps`	Yes
`outputs`	Yes
`warnings`	Yes
`normalized`	No
`provenance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / description

Previous value: -"数字最好写成字符串（十进制，如 \"12.5\"），JSON 数字也行；千位逗号只认 1,234,567 这种写法，小数点用英文句点，不要带货币符号或单位。币种可写 USD、usd 或 美元，单位可写 cm 或 厘米，日期可写 2026-05-01、2026/05/01 或 20260501。读不准的一律拒绝并说明原因，绝不猜；回答里的 normalized 列出实际采用的值。 / Figures are best sent as decimal strings such as \"12.5\"; a JSON number is accepted too. A thousands comma only as 1,234,567; the decimal point is a dot; no currency symbols or units. A currency may be USD, usd or 美元, a unit cm or 厘米, a date 2026-05-01, 2026/05/01 or 20260501. Anything that cannot be read in exactly one way is refused with a reason, never guessed; `normalized` in the answer lists what was used."New value: +"数字最好写成字符串（十进制，如 \"12.5\"），JSON 数字也行；千位逗号只认 1,234,567 这种写法，小数点用英文句点，不要带货币符号或单位。币种可写 USD、usd 或 美元，单位可写 cm 或 厘米，日期可写 2026-05-01、2026/05/01 或 20260501。读不准的一律拒绝并说明原因，绝不猜；回答里的 normalized 列出实际采用的值。 / Figures should be sent as decimal strings such as \"12.5\"; a JSON number is accepted too. A thousands comma only as 1,234,567; the decimal point is a dot; no currency symbols or units. A currency may be USD, usd or 美元, a unit cm or 厘米, a date 2026-05-01, 2026/05/01 or 20260501. Anything that cannot be read in exactly one way is refused with a reason, never guessed; `normalized` in the answer lists what was used."

addedInput schema / examples

Added value: +[
+  {
+    "currency": "USD",
+    "destination": "gb",
+    "dutyRate": "2",
+    "freight": "600",
+    "goods": "5000",
+    "insurance": "30",
+    "quantity": "1000",
+    "rate": "0.75",
+    "vatRate": "20"
+  }
+]

AddedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already establish a read-only, idempotent, closed-world operation, so the bar is lower. The description does add genuinely useful context: the datasets it reads (duty-rules@current, uk-tariff@current), the refusal-with-reason policy for unparseable input, the `normalized` echo field, and the requirement to pass on the notice and source line. Return shape and error behavior are otherwise left to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every clause is relevant, but the full English/Chinese duplication roughly doubles the length, and the format rules repeat what the input schema's own description already says.

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 nine-parameter calculation tool with an output schema and annotations, the definition covers purpose, data sources, input strictness and legal framing. It does not clarify when the optional `rate` and `dutyRate` become necessary, which is the main remaining ambiguity for an agent assembling the call.

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 the schema already documents all nine parameters and their decimal-string patterns. The description reinforces the accepted numeric and currency formats but adds no per-parameter meaning beyond what the schema states, which lands at the baseline.

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 description gives a specific verb and resource: compute the duty and VAT a buyer pays on a consignment to the UK, plus the landed cost. That distinguishes it from pure conversion helpers like fx-convert, but the overlap with landed-cost siblings such as fx-cost or amazon-fees is left implicit rather than named.

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?

The guidance that exists is about input handling rather than tool selection: ask for missing required figures, omit optional ones, quote provenance.source_line, and pass on the disclaimer. It never says when to prefer this over a sibling estimator or what happens if the destination is outside the UK, so usage is only implied.

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

All 出口单 chukoudan tools Inspect

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

Need Help?