livostyle-catalog-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search Livostyle's women's fashion catalog. Filters by product type, category, tag, price, rating. Returns matching products sorted by relevance. Use this when the user asks for outfits, clothing, accessories, occasion-wear, or budget-constrained shopping. |
| get_productA | Get full details (description, all variants with sizes/colors/prices, images, reviews) for a single Livostyle product by handle. Use after search to expand on a specific item. |
| list_collectionsA | List all curated collections on Livostyle (e.g. Wedding Guest Dresses, Vacation Outfits, Coachella, Boho Style). Returns collection handles and product counts. |
| get_collectionA | Get products belonging to a specific collection. Use after list_collections. |
| recommend_outfitA | Generate an outfit recommendation matched to occasion + budget. Picks 1 dress OR 1 top+1 bottom, plus optional accessories. Returns 1-3 complete outfit suggestions sourced from Livostyle's catalog. |
| catalog_statsA | Return live catalog statistics: total products, collections, avg rating, review counts, top categories. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct and well-defined purpose: catalog_stats gives overview, get_collection and list_collections handle collections, get_product gives full details, recommend_outfit generates outfits, and search_products is the main search. No overlapping or ambiguous boundaries.
Tool names follow a consistent snake_case pattern, mostly verb_noun (get_, list_, recommend_, search_). The only minor deviation is catalog_stats (noun_noun) instead of get_catalog_stats, but it remains clear and predictable.
With 6 tools, the server is well-scoped for a fashion catalog. Each tool serves a clear role, covering search, listing, details, recommendations, and statistics without redundancy or unnecessary complexity.
The tool set covers all essential operations for a read-only catalog: searching, browsing collections, getting product details, and even outfit recommendations. There are no obvious gaps for the stated domain.