sunleaf
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUNLEAF_DATA_DIR | No | Optional path to the data directory containing products.json, faqs.json, and policies/. If not set, the built-in sample data is used. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search the Sunleaf Tea Co. catalog by keywords such as a tea type, flavour, occasion or teaware item. Returns matching products with id, category, price in INR and USD, sizes and stock status. Use get_product for full details. |
| get_productA | Full details for one Sunleaf product by its id (from search_products): description, sizes, tags, price and stock. |
| search_faqsA | Find the Sunleaf FAQ entries that best match a question. Returns each question and answer with its FAQ id for citation. |
| get_policyA | The full text of one Sunleaf store policy as Markdown: shipping, returns, privacy or wholesale. |
| answer_sourcesA | Search the FAQs and policies together for a customer question. Returns passages with ids to cite, marked as answers or as partial matches, plus the scope rules of any policy they come from or are governed by. A partial match can still answer by exclusion: a list of the countries the shop ships to answers whether it ships somewhere else. If nothing matches, it says so: tell the customer instead of guessing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| customer_reply | Draft a reply to a customer message using only the Sunleaf tools and sources, with citations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | Every Sunleaf Tea Co. product (fictional demo data). |
| faqs | Every Sunleaf Tea Co. FAQ (fictional demo data). |
| policy-shipping | Shipping, returns, privacy and wholesale policies (sample text). |
| policy-returns | Shipping, returns, privacy and wholesale policies (sample text). |
| policy-privacy | Shipping, returns, privacy and wholesale policies (sample text). |
| policy-wholesale | Shipping, returns, privacy and wholesale policies (sample text). |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: FAQ search, product search, product detail retrieval, policy retrieval, and a combined answer tool that searches both FAQs and policies with citations. Even though search_faqs and answer_sources overlap on FAQs, answer_sources is broader and returns different output, so there's no real ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (search_faqs, search_products, get_product, get_policy, answer_sources). The pattern is predictable and uniform throughout.
With 5 tools, the server is well-scoped for a read-only customer support context covering products, FAQs, and policies. Each tool serves a necessary role, and the count is neither too thin nor excessive.
The surface fully covers the domain: product search and details, FAQ search, policy retrieval, and a combined answer tool that handles cross-domain queries. There are no obvious missing operations for the stated purpose of answering customer questions.