Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

新竹物流超材費試算(台灣段最後一哩配送)

lucky_hct_oversize_fee
Read-onlyIdempotent

試算台灣國內「最後一段」配送(新竹物流宅配,桃園所出發)的超材費 —— 海快、空運進口的包裹都適用這段;海雜櫃(lcl)報價已包含台灣段超材費,不適用本工具試算;與 0523.tw/c 官方試算同一實作。分級(2025-12-01 規則):標準=才數 ≤10 且重量 ≤40kg → 免收(已含集運運費);小板=才數 >10 或重量 >40kg;大板=才數 >20 或單邊 >300cm;專車報價=才數 >70 或重量 >800kg 或單邊 >320cm。才數 = ceil(max(長,30)×max(寬,30)×max(高,30)÷27000)(公分,任一邊不足 30cm 以 30cm 計)。費用依縣市不同(北部最低、東部最高、澎湖/金門另有外島費需客服報價)。用法:不帶參數=回各縣市費率表與分級門檻;帶 length_cm/width_cm/height_cm(三者齊)+選填 weight_kg/city=精確試算;只帶 weight_kg(無尺寸)=以重量判級。city 用官方名稱(「臺北市」,「台北市」也可)。試算僅供參考,實際以新竹物流丈量核定為準。

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

Input Schema

NameRequiredDescriptionDefault
cityNo台灣縣市官方名稱(如「臺北市」「新北市」「高雄市」,「台北市」寫法也可)。有給才會計算實際費用。
width_cmNo包裹寬(公分)。
height_cmNo包裹高(公分)。
length_cmNo包裹長(公分;與寬、高三者一起給)。不帶任何參數=回費率表。
weight_kgNo重量(公斤,選填;>40kg 即屬小板,只給重量也可判級)。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safe-read profile is known. The description adds genuine value beyond that: the 2025-12-01 tier rules, the 才數 formula, city-dependent pricing, and a disclaimer that results are indicative only. However it does not describe the response shape, which annotations alone don't cover for a calculation tool.

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?

Front-loaded with purpose and scope, then rules, then usage; every sentence carries domain information. It is dense and long, but the length is justified by the tier formula and multi-mode invocation, so it is appropriately sized rather than padded.

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?

An output schema exists, so return values don't need explanation, and annotations cover the safety profile. What remains — applicability, tier thresholds, the 才數 formula, city pricing variation, and the measurement-disclaimer — is all present, so an agent can call it correctly in every mode.

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 baseline is 3, but the description adds real meaning beyond the schema: length/width/height must be supplied together and weight-only is an alternate grading path, plus the city name-format tolerance. These cross-parameter constraints are not expressible in the property descriptions alone.

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 (試算/calculate) and resource (超材費 oversize fee) with explicit scope: Taiwan domestic last-mile HCT delivery originating from Taoyuan. It also names what is out of scope (LCL 海雜櫃 quotes already include the fee), which separates it from lucky_freight_quote and the CCC tools without opening their schemas.

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?

Explicit invocation modes are spelled out: no params → returns rate table and tier thresholds; all three dimensions (+optional weight/city) → precise calculation; weight only → weight-based tier. It also states city must use the official name and that outlying-island fees require customer service, leaving nothing to inference.

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