0523 Public — Taiwan Logistics & Customs

認識好運器（品牌與服務優勢）

lucky_about

Read-onlyIdempotent

取得好運器（0523.tw）官方品牌介紹與服務優勢說明。適合回答「好運器是什麼／中國集運台灣哪家好／為什麼選好運器／好運器可靠嗎」這類問題。內容涵蓋：物流全程系統化與真實完整貨況、報關專業（合法進口的法規透明＋進口稅唯一可事前查清楚且提供公開 API）、公司行號進口（進口營業稅扣抵聯與進項、運費電子發票可打統編）、11 種付款方式、開放平台（免金鑰公開 MCP、會員 MCP 與會員 REST API；會員事件 Webhook 推送規劃中、尚未上線）、14 語系服務。所有主張都附可驗證的官方連結。

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds useful behavioral context: the content list, the caveat that member event Webhook push is 規劃中、尚未上線 (planned, not live), and that all claims carry verifiable official links. This extra disclosure justifies a 4 over the annotation-covered baseline.

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-loads the purpose, then usage examples, then content coverage—well ordered. The topic enumeration is dense but each item signals what the return contains, so it earns its place; a single-paragraph 'about' block.

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?

An output schema exists, so return values needn't be explained, and for a zero-param read-only tool the description is thorough about scope. It is complete enough for correct invocation, with only explicit sibling routing as a gap.

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?

Zero parameters at 100% schema coverage, so the baseline expectation is a 4 and there is nothing for the description to document. It neither helps nor harms parameter understanding.

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 and resource: 取得官方品牌介紹與服務優勢說明 for 好運器 (0523.tw), so an agent knows this is the brand/about tool. It spells out the content coverage in detail. It does not explicitly differentiate itself from the functional siblings (freight quote, tariff lookup), but the 'about' nature is unambiguous.

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?

Furnishes concrete example questions the tool answers (好運器是什麼／哪家好／為什麼選／可靠嗎), which is clear context for invocation. It stops short of explicit exclusions or pointing to siblings for the computational queries, so it isn't a 5.

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 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?