Skip to main content
Glama

0523 Public — Taiwan Logistics & Customs

by tw.0523
OverviewDiscussionsAdmin

有斑 YOUBAN 新鮮龍虎斑（第三方商家）

lucky_youban_seafood
Read-onlyIdempotent

取得「有斑 YOUBAN」新鮮龍虎斑（珍珠龍膽石斑）的商品規格與訂購規則：品名、單尾重量範圍、處理方式（三去）、真空冷凍包裝、保存溫度、秤重計價公式、最低訂購量 5 尾起、產地，以及四步驟的 LINE／電話訂購流程。適合回答「龍虎斑一斤多少錢」「石斑魚宅配怎麼買」「有斑 YOUBAN 是什麼」這類問題。⚠️ 有斑是刊登在好運器（0523.tw）平台上的第三方商家，商品由高雄韋泉有限公司提供，好運器不參與銷售與出貨。⚠️ 本工具不提供即時庫存、不能下單——現貨與到貨時間請洽商家 LINE。運費、配送範圍與付款方式本站不代為承諾。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNo選填。要查的專業主題，不帶則回傳商品規格、訂購規則與可用主題清單。可用值：quality（挑選與品質判斷）、storage（保存與解凍）、safety（食品安全：中心溫度、寄生蟲、雪卡毒、藥物殘留）、nutrition（營養與適用族群）、cooking（料理專業）、industry（產業知識：品種、產地、產季）、myths（常見誤解）。

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": "選填。要查的專業主題，不帶則回傳商品規格、訂購規則與可用主題清單。可用值：quality（挑選與品質判斷）、storage（保存與解凍）、safety（食品安全：中心溫度、寄生蟲、雪卡毒、藥物殘留）、nutrition（營養與適用族群）、cooking（料理專業）、industry（產業知識：品種、產地、產季）、myths（常見誤解）。",
+  "maxLength": 40,
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds meaningful context beyond that: it is a third-party merchant hosted on the 0523.tw platform with fulfillment by 高雄韋泉有限公司, and the platform does not participate in sales or shipping. It also disclaims commitments on freight, delivery range, and payment.

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 purpose and the retrieved fields are front-loaded, and warnings are set off with ⚠️ markers for scannability. It is fairly dense and long, but most sentences carry substantive constraints rather than filler.

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?

With an output schema present, return values need not be explained, and the description covers scope, merchant identity, and explicit limitations. An agent has enough to decide to call it and to warn the user it cannot transact. Only named alternatives to sibling tools are absent.

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 single 'topic' parameter is fully documented in the schema, including all enum-like values. The description adds no additional meaning about the parameter, so the baseline of 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 states a specific verb and resource: it retrieves product specifications and ordering rules for the named 'YOUBAN' grouper product, enumerating exactly what is returned (name, weight range, processing method, packaging, storage temperature, pricing formula, minimum order, origin, ordering steps). This is highly specific and clearly differentiates it from the freight/tariff/declaration siblings.

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 when-to-use example questions ('一斤多少錢', '宅配怎麼買', 'YOUBAN 是什麼') and an explicit when-not: no real-time stock and no ordering, directing stock inquiries to the merchant LINE. No named sibling alternatives are offered, which keeps it short of 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 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