Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

CCC 稅則號別查詢(稅率+輸入規定)

lucky_ccc_tariff_lookup
Read-onlyIdempotent

用台灣 CCC 稅則號別(4–11 碼,可含小數點)查完整稅費與輸入規定,與官方稅則搜尋頁 https://0523.tw/search 同一份資料與解析:貨名、進口關稅(第一欄/第二欄 ECFA·FTA,稅率可能為 0% 但所有進口貨物都適用)、營業稅 5%(一律課徵)、依稽徵規定的貨物稅(T/T*,含條號與稅率)、酒稅(B/B*)、菸稅及菸品健康福利捐(C)、特種貨物及勞務稅(L*)、反傾銷稅提示、推廣貿易服務費 0.04%,以及輸入規定代碼與主管機關說明(如 F01 食藥署、C02 BSMI)。資料來源:財政部關務署(每週同步)。

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_ccc_tariff_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo使用者對話用的語言(選填):zh-TW、en、ja、ko、vi、ms、th、id、hi、es、pt、de、fr、ru。帶了之後,回應裡的好運器網址會開啟該語言的頁面。
ccc_codeNo必填。台灣 CCC 稅則號別 4–11 碼,可含小數點與檢查碼(如 3304.99.90.00-5、33049990、8471.30)。

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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior. Beyond them the description discloses the authoritative data source (Customs Administration), weekly sync cadence, equivalence to the official search page, and important tax semantics such as 0% tariff still applying and 5% business tax always being levied. It does not cover partial-code/ambiguity behavior or error handling, so not a 5.

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?

The purpose and input constraints are front-loaded, and the dense enumeration of tax components gives a quick scope signal. The single long sentence packs in many output details that an output schema may already cover, but it remains readable and largely earns its space.

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?

With an output schema and rich annotations, the description does a solid job covering data provenance, freshness, return scope, and tax caveats. The main missing pieces are how ambiguous or partial CCC codes are handled and when to choose this over sibling estimation/prediction tools.

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%, and the schema already documents ccc_code's length, decimal/check-digit formats, and lang's supported language list and URL-language effect. The description mostly restates the CCC code format and does not add new meaning for either parameter, so baseline 3 applies.

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 opens with a specific verb-resource pair ('用...查...') and names the exact lookup key (Taiwan CCC 4–11 digit code), plus enumerates returned tax and import-regulation fields. It does not explicitly contrast with siblings such as lucky_ccc_predict or lucky_import_tax_estimate, so it falls short of the top 'distinguishes from siblings' criterion.

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?

It implies usage by saying to look up via a CCC code and points to the official search page as equivalent data, giving context for when the tool is appropriate. However, it provides no explicit when-not conditions and never names alternatives, so an agent must infer that this is for code-based tariff lookup rather than code prediction or total landed-cost estimation.

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