Skincare Recommendation MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search the store's product catalog by skin type and/or skincare concern. Args: skin_type: e.g. "grasa", "seca", "mixta", "sensible", "normal". Empty to skip this filter. concern: e.g. "acné", "manchas", "arrugas", "sensibilidad", "hidratación". Empty to skip this filter. in_stock_only: only return products currently in stock. |
| get_product_detailsA | Get full details (price, stock, active ingredients) for one product by its id. |
| find_alternativesA | Find other in-stock products sharing at least one active ingredient with the given product - useful when it's out of stock or the client wants a different brand with the same effect. |
| check_ingredient_conflictsA | Check whether a candidate product's active ingredients conflict with ingredients the client already uses. Args: current_ingredients: active ingredients in the client's current routine. candidate_ingredients: active ingredients of the product being considered. |
| recommend_productsA | End-to-end recommendation: find in-stock products matching the client's skin type and concerns, and flag any that conflict with their current routine. Args: skin_type: client's skin type, e.g. "grasa". concerns: concerns to address, e.g. ["acné", "manchas"]. current_ingredients: active ingredients already in the client's routine. |
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 5 tools
Most tools map to clearly distinct tasks: catalog search, product details, alternatives, conflict checking, and full recommendations. The only notable ambiguity is between search_products and recommend_products, since the latter includes the former's filtering behavior plus conflict flagging, but the descriptions make the distinction recoverable.
All tool names follow a consistent verb_noun snake_case pattern: search_products, get_product_details, find_alternatives, check_ingredient_conflicts, recommend_products. No mixed naming conventions or vague verbs.
Five tools is a well-scoped size for a specialized skincare recommendation server. Each tool addresses a distinct step in the workflow without redundancy or bloat.
The tool surface covers the full recommendation workflow: searching/filtering, retrieving details, finding alternatives, checking ingredient conflicts, and generating end-to-end recommendations. No obvious dead ends or missing operations for the stated purpose.