Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

by tw.0523
OverviewDiscussionsAdmin

漢清旗袍服飾店・台北手工訂製（第三方商家）

lucky_hanching_qipao
Read-onlyIdempotent

取得台北「漢清旗袍服飾店」的服務項目與預約規則：手工訂製旗袍、旗袍租借、唐裝與中式禮服，含租借價格區間、訂製工期（1～1.5 個月）、預約前置時間（一般試穿 1～2 週、婚禮用途一個月）、量身到取件的完整流程、店址與營業時間。適合回答「台北哪裡可以訂製旗袍」「旗袍租借多少錢」「訂做旗袍要多久」這類問題。⚠️ 訂製價格店家未公開，需到店量身後報價——請不要引用網路上流傳的舊數字。⚠️ 漢清是刊登在好運器（0523.tw）平台上的第三方商家，好運器不參與其服務提供或報價。⚠️ 本工具無法代為預約，量身需親自到店。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNo選填。要查的專業主題，不帶則回傳基本資訊與可用主題清單。可用值：fitting（量身與版型）、fabric（布料）、craft（工藝辨識）、care（保養）、occasion（場合與禮儀）、rent_vs_custom（訂製或租借怎麼選）、chinese_bridal（秀禾服／龍鳳褂／旗袍的差別）、taiwan_history（旗袍在台灣的脈絡）。

Output Schema

TableJSON 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 / topic
      Added value: +{
+  "description": "選填。要查的專業主題，不帶則回傳基本資訊與可用主題清單。可用值：fitting（量身與版型）、fabric（布料）、craft（工藝辨識）、care（保養）、occasion（場合與禮儀）、rent_vs_custom（訂製或租借怎麼選）、chinese_bridal（秀禾服／龍鳳褂／旗袍的差別）、taiwan_history（旗袍在台灣的脈絡）。",
+  "maxLength": 40,
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses genuinely useful behavioral context: custom prices are unpublished and require in-store measurement (do not cite old online figures), the shop is a third-party merchant on the 0523.tw platform that does not itself provide the service, and the tool cannot make reservations. These caveats materially shape how the agent should use and report the data.

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?

Content is front-loaded with what is retrieved, then caveats, then example questions. Sentences largely earn their place, though the three ⚠️ warnings and example-question list make it longer than strictly necessary; still efficient for the risk of misquoting prices.

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?

With an output schema present, return-value detail is unnecessary, and annotations cover the safety profile. The description fills the remaining gaps an agent needs — price-opacity warning, no-booking limitation, third-party disclaimers — leaving nothing essential unstated.

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 description coverage is 100% and the schema itself enumerates every allowed topic value (fitting, fabric, craft, care, occasion, rent_vs_custom, chinese_bridal, taiwan_history) plus the empty-default behavior. The description adds nothing about the topic parameter, so the baseline 3 applies.

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?

The description names a specific resource (台北「漢清旗袍服飾店」的服務項目與預約規則) and enumerates exactly what is retrieved: services, rental price ranges, custom lead times, the full fitting-to-pickup process, address and hours. It is clearly distinguishable from generic siblings like lucky_about or lucky_freight_quote.

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?

It gives concrete usage contexts with example questions (「台北哪裡可以訂製旗袍」「旗袍租借多少錢」) and states clear boundaries (cannot book appointments, fitting requires in-person visit). It stops short of naming an alternative sibling tool, so it lacks explicit when-not/alternatives routing.

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