
Natural-language fashion search and complete outfits from real shop pieces. Anonymous, read-only.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use this when the user wants a complete outfit. Primary chat path is prompt-based generation; widget actions may call this with product_id for item-based outfit generation. Pass `gender` when you know who the outfit is for. Do not use this for single-item product search. The result's `content` is a plain-text summary of the outfit (each piece with brand and price); `structuredContent.outfit` holds the same pieces with product ids and shop links.
Who the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests.
Total outfit budget in EUR. Pass the user's budget when they give one, and a high one (e.g. 3000) when they ask for designer or luxury pieces. Omitted, the outfit is kept to about EUR 700.
Use this when the user wants a complete outfit. Primary chat path is prompt-based generation; widget actions may call this with product_id for item-based outfit generation. Pass `gender` when you know who the outfit is for. Do not use this for single-item product search. The result's `content` is a plain-text summary of the outfit (each piece with brand and price); `structuredContent.outfit` holds the same pieces with product ids and shop links.
| Argument | Type | Description |
|---|---|---|
| image | any | |
| gender | any | Who the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests. |
| prompt | any | |
| max_budget | any | Total outfit budget in EUR. Pass the user's budget when they give one, and a high one (e.g. 3000) when they ask for designer or luxury pieces. Omitted, the outfit is kept to about EUR 700. |
| product_id | any |
{
"type": "object",
"properties": {
"image": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"gender": {
"anyOf": [
{
"enum": [
"female",
"male"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Who the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests."
},
"prompt": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"max_budget": {
"anyOf": [
{
"type": "number"
},
{
"type": "null"
}
],
"default": null,
"description": "Total outfit budget in EUR. Pass the user's budget when they give one, and a high one (e.g. 3000) when they ask for designer or luxury pieces. Omitted, the outfit is kept to about EUR 700."
},
"product_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
}Use this when the user wants to find specific fashion products (clothing, footwear, accessories) by text, optionally guided by images. Pass `gender` when you know who the clothes are for. Do not use this for full outfit generation or visualization-only requests. The result's `content` is a plain-text list of the products (brand, price); `structuredContent.products` holds the same products with ids and shop links.
| Argument | Type | Description |
|---|---|---|
| query* | string | |
| gender | any | Who the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests. |
| images | any |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string"
},
"gender": {
"anyOf": [
{
"enum": [
"female",
"male"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Who the clothes are for: 'female' or 'male'. Set it whenever the user says or the conversation suggests it ('for my boyfriend', 'women's', a gender they mentioned earlier, the kind of piece they ask for). Only ask the user if there is no hint at all and the answer would clearly differ by gender. Omit for unisex requests."
},
"images": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
}