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?

Annotations already declare the tool read-only and idempotent, and the description adds valuable behavioral limitations: prices are not public, the platform is a third-party listing, and the tool cannot book appointments. These caveats go beyond the annotations and prevent the user from expecting real-time pricing or booking capability.

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 description is a compact block that front-loads the main purpose and uses bold warnings to highlight critical caveats. It's slightly long but every sentence adds substantive information about the store's services, process, or limitations, so it earns its length.

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?

For a tool with one optional parameter and an output schema, the description is remarkably complete: it covers service types, rental price ranges, customization lead times, appointment lead times, the full process from measuring to pickup, address, business hours, and third-party disclaimers. The output schema handles return values, so no further explanation is needed.

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?

The schema has 100% coverage for the single optional 'topic' parameter, which is fully described with allowed values. The description does not mention the parameter or provide additional usage details, so it adds no semantic value beyond what the schema already provides. Baseline of 3 is appropriate.

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 clearly states the tool retrieves service offerings and booking rules for a specific Taipei qipao shop, using a specific verb ('取得') and naming the resource. It distinguishes itself from unrelated sibling tools by its niche topic and detailed scope.

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 explicitly lists example question types the tool can answer ('台北哪裡可以訂製旗袍', '旗袍租借多少錢', etc.), providing clear when-to-use context. It also warns against using outdated pricing information, but does not name alternative tools because none are close substitutes.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources