hou-tea
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOU_TEA_API_BASE | No | Override API host (e.g. for staging). | https://hou-tea.com |
| HOU_TEA_PAY_BASE | No | Override x402 middleware host. | https://hou-tea.com/pay |
| HOU_TEA_STORE_ID | No | Default store_id. | fengshui |
| HOU_TEA_AGENT_KEY | No | Optional X-Agent-Key for higher rate limits / private skills. Contact support@hou-tea.com. |
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
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hou_tea_browseB | [core] Browse the hou-tea Chinese tea catalog. Returns products with name, price (USD/USDC), images, taste profile, fermentation level, season, and a ready-to-render |
| hou_tea_recommendA | [core] Get curated tea recommendations from a natural-language query. Returns ranked products with explanation. Best entry point when the user asks 'recommend me a tea for X' or describes a mood / occasion / use-case. |
| hou_tea_explainA | [core] Returns origin story, brewing guide (water temp, steep time, ratio), health benefits, talking points, cultural context, and cross-sell suggestions for one product. |
| hou_tea_get_payment_requirementsB | [core] Initiate an x402 USDC payment intent for a product. Returns HTTP 402-style payment requirements (recipient address, amount, Base chain network). Auto-includes buyer order grouping ( |
| hou_tea_check_orderA | [core] Poll the status of a previously created order. Status transitions: pending_payment → verifying → confirmed (after on-chain USDC settlement). Use exponential backoff (~2s, 4s, 8s …, max ~60s). |
| hou_tea_list_my_ordersC | [core] List USDC/x402 orders associated with the buyer_list_token (returned from a successful purchase or stored in env HOU_TEA_BUYER_LIST_TOKEN). No merchant API key required. |
| hou_tea_discover_extendedA | [meta] Reveal extended tools (compare / health-filter / agent-card) by adding them to tools/list. Optionally filter by |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Hou Tea Recommendation Grid | Displays product recommendations and follow-up actions. |
| Hou Tea Payment Review | Reviews x402 payment requirements before wallet handoff. |
| Hou Tea Order Timeline | Displays order status, payment state, and tracking progress. |
TDQS
Scored across 7 tools
Each tool serves a unique function: browsing catalog, checking orders, discovering extended tools, explaining products, initiating payment, listing orders, and recommending teas. No functional overlap exists.
All tools follow the 'hou_tea_verb_noun' pattern in snake_case, e.g., hou_tea_browse, hou_tea_check_order, hou_tea_discover_extended. Naming is uniform and predictable.
With 7 tools, the surface is well-scoped for a tea e-commerce server covering browsing, recommendations, explanations, payments, and order management. No excess or deficiency.
The core workflow of browse, recommend, explain, pay, and track orders is covered. However, there is no explicit order creation tool (though payment initiation implies it) and missing cancellation/update capabilities, which are minor gaps.