demo-plant-shop
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_help_articlesA | Search Demo Plant Shop policies and plant care guides by keyword. Returns ranked article IDs, titles and snippets. Use get_help_article to read the full article. |
| get_help_articleA | Read the full text of one Demo Plant Shop help article using an article ID from search results or resources. |
| get_order_statusA | Read the status of a fictional order. Requires the order reference and the matching email supplied by the customer. |
| find_plantsA | Find catalog plants for low, medium or bright light. Optionally filter by whether they are pet-safe and by a maximum price in demo credits. |
| create_return_requestA | Preview a return request for a delivered order with matching email and a customer-provided reason. Submit with confirm=true only after the customer explicitly confirms the preview. Repeating a submission returns the existing request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| answer_customer_question | Prepare a grounded answer to a Demo Plant Shop customer question. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| care-01 | |
| care-02 | |
| care-03 | |
| care-04 | |
| care-05 | |
| care-06 | |
| care-07 | |
| care-08 | |
| ship-01 | |
| ship-02 | |
| ship-03 | |
| ship-04 | |
| ship-05 | |
| ship-06 | |
| pickup-01 | |
| pickup-02 | |
| order-01 | |
| order-02 | |
| return-01 | |
| return-02 | |
| return-03 | |
| return-04 | |
| return-05 | |
| pay-01 | |
| pay-02 | |
| pay-03 | |
| gift-01 | |
| gift-02 | |
| contact-01 | |
| stock-01 |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: help search vs. help reading, order status lookup, plant catalog filtering, and return submission. The one potentially confusable pair (search_help_articles vs. find_plants) is separated by domain—policy content versus catalog inventory—and the descriptions make that explicit.
All five tools follow a clean verb_noun snake_case pattern (search_help_articles, get_help_article, get_order_status, find_plants, create_return_request). Verbs are semantically accurate and the shared prefixes (help_, order) group related tools predictably.
Five tools is a tight, well-scoped surface with no redundant entries, appropriate for a demo shop assistant. It leans slightly thin—there is no purchasing or cart operation—but every listed tool earns its place.
The surface covers discovery (help, plants), post-purchase status, and returns, but skips the core commerce step: there is no way to place an order or view a customer's order list. An agent handling an end-to-end shopping request would hit a dead end before checkout.