Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

台灣進口稅金試算

lucky_import_tax_estimate
Read-onlyIdempotent

試算進口台灣的法定稅費,與 0523.tw 官方試算(/c/、/search 同一資料)一致:進口關稅(所有貨物都適用,稅率可能為 0%)+營業稅 5%(一律課徵)+依稽徵規定自動判定的貨物稅(T/T*)/酒稅(B/B*,需 volume_liters 與 alcohol_degree)/菸稅及菸品健康福利捐(C,需 tobacco_sticks;菸絲、雪茄的健康福利捐依 weight_kg 計,健康福利捐併入營業稅稅基)+推廣貿易服務費 0.04%,並判斷 NT$2,000 小額免稅(菸酒不適用;同一納稅義務人每半年度〔1–6 月、7–12 月〕免稅放行逾 6 次後,第 7 次起不適用)。必填 currency_code 與 price_foreign;hs_code 沒給時可用 product_description 讓 AI 自動分類。回傳含海關旬別匯率換算、稅費細項、總落地成本(不含台灣段新竹物流超材費——大型包裹不分海快/空運另計)。金額 TWD,僅供參考,實際以海關核定為準。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lucky_import_tax_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo使用者對話用的語言(選填):zh-TW、en、ja、ko、vi、ms、th、id、hi、es、pt、de、fr、ru。帶了之後,回應裡的好運器網址會開啟該語言的頁面。
hs_codeNoCCC 稅則號別 4–11 碼(選填)。
quantityNo數量,預設 1。
width_cmNo寬(公分)。
height_cmNo高(公分)。
length_cmNo長(公分,選填;三個尺寸一起給才會算材積)。
weight_kgNo重量(公斤,選填;有給會一併算運費)。
currency_codeNo必填。商品計價幣別 3 碼代碼,如 CNY、USD、JPY、EUR、TWD。
price_foreignNo必填。外幣計價的商品金額(會依海關旬別匯率換算 TWD)。
shipping_modeNo運送方式:sea 海快(預設)/ air 空運。
volume_litersNo酒類容量(公升,酒類才需要)。
alcohol_degreeNo酒精度 %vol(酒類才需要)。
tobacco_sticksNo菸支數(菸品才需要)。
insurance_foreignNo保險費(外幣,選填)。
over_exempt_limitNo本半年度(1–6 月或 7–12 月)已免稅放行 6 次、本件為第 7 次起(不再適用 NT$2,000 免稅)→ true 強制課稅試算。
product_descriptionNo商品名稱/描述(選填)。沒給 hs_code 時會用 AI 自動分類出 CCC 稅則。

Output Schema

NameRequiredDescriptionDefault
dataYes完整結構化結果。欄位依工具而異,與 content[0].text 內附的 JSON 完全相同。
sourceYes資料來源,固定為 0523.tw。引用時請註明。
summaryYes一行白話結論,已把關鍵數字算好,可直接引用回覆使用者;無摘要時為空字串。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "使用者對話用的語言(選填):zh-TW、en、ja、ko、vi、ms、th、id、hi、es、pt、de、fr、ru。帶了之後,回應裡的好運器網址會開啟該語言的頁面。",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / hs_code / description
      Previous value: -"CCC 稅則號別 4–11 碼(選填)。可先用 lucky_ccc_predict 查。"New value: +"CCC 稅則號別 4–11 碼(選填)。"
  3. Changed1 schema field changed
    • changedInput schema / properties / over_exempt_limit / description
      Previous value: -"半年內已進口逾 6 次(免稅額度用完)→ true 強制課稅試算。"New value: +"本半年度(1–6 月或 7–12 月)已免稅放行 6 次、本件為第 7 次起(不再適用 NT$2,000 免稅)→ true 強制課稅試算。"
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description goes far beyond by disclosing the NT$2,000 exemption logic (alcohol/tobacco excluded, six duty-free releases per half-year, no exemption from the 7th), customs 10-day-period FX conversion, and that results are estimates subject to customs' final determination. It also flags what is deliberately NOT in the returned total (HCT oversize fee for large parcels).

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?

Purpose and fee composition are front-loaded and every clause carries real information for a 16-parameter tax tool. The middle is a dense run-on of nested parentheses that would read better as a short list, but there is little filler to cut.

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 16-parameter domain-specific calculator with an output schema, the description covers the tax-determination rules, the conditional parameter requirements, the exemption logic, and the estimate-only caveat. Nothing an agent needs to call it correctly 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 domain meaning the schema does not: volume_liters+alcohol_degree are tied to alcohol tax (B/B*), tobacco_sticks to tobacco tax and the health levy (C), and weight_kg to the levy on cigars/loose tobacco, plus the hs_code-vs-product_description fallback. This mapping tells the agent which optional parameters actually matter for a given product.

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?

States a specific verb+resource: estimating Taiwan import statutory taxes/fees, and enumerates the exact fee components (customs duty, 5% VAT, commodity/alcohol/tobacco taxes, 0.04% trade promotion fee). It implicitly separates itself from siblings by noting the total landed cost excludes the Taiwan-leg HCT oversize fee, which points at lucky_hct_oversize_fee, though no sibling is named explicitly.

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 concrete invocation conditions: currency_code and price_foreign are required, and if hs_code is omitted the agent may supply product_description for AI classification. It also states scope boundaries (exemption rules, exclusion of oversize fees), but never explicitly says when to prefer lucky_freight_quote or lucky_simple_declaration instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources