0523 Public — Taiwan Logistics & Customs

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

lucky_youban_seafood

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 2, 2026

addedInput schema / properties / topic

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

AddedAug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description goes beyond these by adding valuable context: the third-party merchant disclaimer, that the platform does not participate in sales/shipping, and that live inventory is not provided. This is consistent with the annotations and adds meaningful behavioral nuance without contradiction.

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 somewhat long (multiple clauses, warnings, and examples), but every segment earns its place: it front-loads the core functionality, then gives example questions, and ends with disclaimers. The structure is logical and the warnings are important for an agent deciding whether to use this tool. It is not verbose despite 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?

Given the tool's simple read-only nature (one optional parameter, output schema present), the description covers everything needed: the exact product, what information is returned, ordering limitations, and the merchant context. The output schema handles return value specifics, so the description need not repeat them. It is a complete and self-contained description.

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 'topic' parameter's description is thorough (lists all allowed values). The tool description does not mention the parameter at all, but the schema already explains it completely. Per the rubric, baseline is 3 when schema covers all parameters, and there is no additional semantic value added by the description.

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 starts with a specific verb '取得' (get) and clearly identifies the resource: '有斑 YOUBAN 新鮮龍虎斑（珍珠龍膽石斑）'. It lists the exact information delivered (specs, ordering rules, pricing, etc.), and the content is unique among siblings, which are unrelated tools. This fully distinguishes it from alternatives.

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?

The description explicitly states when to use it: '適合回答「龍虎斑一斤多少錢」「石斑魚宅配怎麼買」「有斑 YOUBAN 是什麼」這類問題'. It also gives clear when-not guidance: '不提供即時庫存、不能下單' and directs users to the merchant LINE for those cases. This provides both positive and negative usage conditions, effectively guiding the agent.

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

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

Need Help?