mcp-drink-main
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_menuA | 查詢目前所有的飲品品項、價格以及可加料的內容。 當使用者詢問有賣什麼、價格為何、想看菜單或想知道加料選項時，請呼叫此工具。 |
| place_drink_orderA | 執行飲品點餐工具。當使用者表達想喝飲料或點餐時，請呼叫此工具。 參數說明：
|
| list_recent_ordersA | 列出最近的所有訂單資訊，包含 ID、姓名與品項。 刪除或修改訂單前，請先呼叫此工具確認 ID。 |
| find_duplicate_orders_by_nameA | 🔍 搜尋特定人物的重複訂單資料。 當使用者詢問「搜尋個人有重複的資料」、「某人有重複訂單」時，請呼叫此工具。 參數說明：
功能：
|
| search_all_duplicatesA | 🔍 掃描全部訂單，找出所有有重複訂單的人物。 當使用者詢問「全局搜尋重複」、「誰有重複訂單」時，請呼叫此工具。 功能：
|
| get_duplicate_statisticsA | 📊 取得重複訂單的統計資訊。 當使用者詢問「重複訂單統計」、「重複率」時，請呼叫此工具。 功能：
|
| update_drink_orderB | 修改已存在的訂單。當使用者提供訂單 ID 並要求更改內容時使用。
|
| update_order_by_nameA | 根據姓名修改訂單內容。 參數設為選填（None）以處理使用者說「其餘不變」的情況。 |
| delete_drink_orderC | 刪除指定的點餐訂單。
|
| delete_order_by_nameC | 根據姓名刪除訂單。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_menu_resource | 提供完整的飲品清單作為 AI 參考資源 |
TDQS
Scored across 10 tools
Each tool has a distinct purpose: listing orders, finding duplicates by name, searching all duplicates, getting duplicate statistics, updating/deleting by ID or by name, fetching the menu, and placing orders. The update and delete pairs are clearly differentiated by the identifier type (doc_id vs. name), and the duplicate tools are distinguished by scope.
Most tools follow a verb_noun pattern (e.g., list_recent_orders, get_menu, place_drink_order), but there are minor inconsistencies such as using both 'find_' and 'search_' for similar duplicate operations, and 'update_drink_order' versus 'update_order_by_name' where the object naming varies. Overall the pattern is readable but not perfectly uniform.
With 10 tools, the server is well-scoped for the drink ordering and duplicate-detection domain. Each tool serves a necessary function, and the count is neither too sparse nor overwhelming.
The tool surface covers the full CRUD lifecycle for orders (place, list, update, delete), includes menu retrieval, and provides comprehensive duplicate detection and statistics. No obvious gaps exist for the intended functionality.