Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

by tw.0523
OverviewDiscussionsAdmin

好運器集運運費試算

lucky_freight_quote
Read-onlyIdempotent

試算好運器（0523.tw）中國→台灣集運運費，與官方試算機 https://0523.tw/c/ 同一份後端實作。金額一律新台幣 TWD。method 可選 sea 海快（預設）、air 空運、lcl 海雜櫃。規則：海快 計費重＝max(實重, 材積重) 無條件進位至整數公斤，材積重＝長×寬×高(cm)÷10000，實際重量未滿 10 kg 加收 NT$100 小包派件費；空運「只計實重」（不計材積），計費重＝實重無條件進位，實重未滿 10 kg 加收 NT$120；海雜櫃只回起價（每公斤 NT$25 起或每材積 NT$150 起，材積＝長×寬×高(cm)÷28316），運費依商品不同、需由客服報價，本工具不提供海雜櫃的確定金額。不帶任何參數＝回傳現行費率表；海快帶 weight（kg）或 length/width/height（cm，三者齊）、空運帶 weight ＝實際試算；method=lcl 一律回海雜櫃起價與報價前要準備的資料（有給尺寸時附材積數；尺寸須三者齊），不論有沒有帶 weight 或尺寸。成功回應都帶 continue_url（接續網址）：費率表與海快／空運試算結果指向官方試算機（試算結果的網址會預填已提供的重量與尺寸；試算機要填齊長、寬、高與重量才會顯示金額），海雜櫃指向客服聯絡頁 https://0523.tw/contact。試算僅供參考，實際以入倉丈量後帳單為準。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo包裹寬（公分）。
heightNo包裹高（公分）。
lengthNo包裹長（公分，三個尺寸要一起給；海快計材積重、海雜櫃算材積數用，空運不採計）。
methodNo運送方式：sea 海快（預設）/ air 空運（只計實重，必帶 weight）/ lcl 海雜櫃（只回起價、需客服報價，不提供確定金額）。
weightNo包裹實際重量（公斤）。海快、海雜櫃可與尺寸擇一；空運必填。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / length / description
      Previous value: -"包裹長（公分，三個尺寸要一起給；僅海快計材積用，空運不採計）。"New value: +"包裹長（公分，三個尺寸要一起給；海快計材積重、海雜櫃算材積數用，空運不採計）。"
    • changedInput schema / properties / method / description
      Previous value: -"運送方式：sea 海快（預設）/ air 空運（只計實重，必帶 weight）。"New value: +"運送方式：sea 海快（預設）/ air 空運（只計實重，必帶 weight）/ lcl 海雜櫃（只回起價、需客服報價，不提供確定金額）。"
    • changedInput schema / properties / method / enum
      Previous value: -[
-  "sea",
-  "air"
-]New value: +[
+  "sea",
+  "air",
+  "lcl"
+]
    • changedInput schema / properties / weight / description
      Previous value: -"包裹實際重量（公斤）。海快可與尺寸擇一；空運必填。"New value: +"包裹實際重量（公斤）。海快、海雜櫃可與尺寸擇一；空運必填。"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the actual pricing formulas (材積重 = L×W×H÷10000, ÷28316 for lcl), the small-package surcharges (NT$100/NT$120), that lcl never returns a definitive amount, and that every response carries a continue_url with pre-filled fields. This is exactly the extra context annotations cannot provide.

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?

Dense and front-loaded with the resource and currency before the rules, and every clause carries operational detail. It is nonetheless one long block paragraph, so rule grouping (per-method) would make it easier to scan than an undifferentiated wall of text.

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?

Given five optional params, an output schema, and rich annotations, the description covers everything an agent needs: valid input combinations, per-method computation, the lcl caveat, the continue_url handoff, and a disclaimer that quotes are estimates pending warehouse measurement.

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 already 100%, but the description adds real meaning: which parameter combinations are valid per method, that dims must be supplied as a trio, and that air ignores dims entirely. It stops short of restating units/ranges, so it is additive rather than redundant.

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?

States a specific verb (試算) and resource (好運器中國→台灣集運運費), names the backing service, and identifies the official calculator it mirrors. An agent can distinguish it from sibling tools like lucky_ccc_tariff_lookup or lucky_import_tax_estimate by domain and output currency (TWD).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly maps every input combination to an outcome: no params returns the current rate table, sea with weight or full dims runs a quote, air requires weight, and lcl always returns starting-price plus what to prepare for a manual quote. It also names the sibling-style alternative routes (official calculator, contact page) for cases the tool cannot price.

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

All 0523 Public — Taiwan Logistics & Customs toolsInspect
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