Skip to main content
Glama

Vitrine: Trending Fashion, Luxury, Sneakers & Design

Find similar items

find_similar
Read-onlyIdempotent

Find alternatives to one item (by id from an earlier result): pieces close in style, the same product type first. Use it for 'something like this but cheaper' (filters.max_price), 'but in stock' (filters.availability) or a different color. The source item is never included. Returns {anchor, count, results} in the search result shape, each with a 'why' naming the shared style. An unknown id returns an error result; an empty list means no alternative passes the filters. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer ') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe item to find alternatives for.
agentNo
limitNo1 to 20. Anonymous callers get at most 5.
filtersNoHard filters. Applied before ranking; an item that fails any of them is never returned.

Output Schema

NameRequiredDescriptionDefault
metaYes
countYes
anchorNo
resultsYes
query_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / filters / properties / subcategory
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 40,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Product type, e.g. 'coat', 'sneakers', 'vase'. Exact values: vocabulary."
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"5 to 20. Anonymous callers get 5."New value: +"1 to 20. Anonymous callers get at most 5."
    • changedInput schema / properties / limit / minimum
      Previous value: -5New value: +1
  3. Changed3 schema fields changed
    • addedInput schema / properties / filters / properties / gender
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "women",
      +        "men",
      +        "unisex"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Department: women, men or unisex. 'men' returns men's and unisex pieces, 'women' returns women's and unisex pieces, 'unisex' returns unisex pieces only. Set gender_exact to true to drop the unisex pieces."
      +}
    • addedInput schema / properties / filters / properties / gender_exact
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "With gender, true matches that department only, without unisex pieces."
      +}
    • addedOutput schema / properties / results / items / properties / gender
      Added value: +{
      +  "description": "Department. Accessories and interior are usually unisex.",
      +  "enum": [
      +    "women",
      +    "men",
      +    "unisex"
      +  ],
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "anchor": {
      +      "properties": {
      +        "brand": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "title": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "count": {
      +      "type": "integer"
      +    },
      +    "meta": {
      +      "properties": {
      +        "access": {
      +          "enum": [
      +            "full",
      +            "basic"
      +          ],
      +          "type": "string"
      +        },
      +        "terms": {
      +          "type": "string"
      +        },
      +        "upgrade": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "query_id": {
      +      "type": "integer"
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "availability": {
      +            "enum": [
      +              "in_stock",
      +              "low_stock",
      +              "preorder",
      +              "out_of_stock"
      +            ],
      +            "type": "string"
      +          },
      +          "brand": {
      +            "type": "string"
      +          },
      +          "category": {
      +            "type": "string"
      +          },
      +          "currency": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "image_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "outbound_url": {
      +            "description": "Tracked link to the retailer's product page. Checkout happens there.",
      +            "type": "string"
      +          },
      +          "price": {
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "trend_score": {
      +            "description": "0 to 100. With a key.",
      +            "type": "integer"
      +          },
      +          "trend_status": {
      +            "description": "With a key.",
      +            "enum": [
      +              "hot",
      +              "rising",
      +              "steady",
      +              "fading"
      +            ],
      +            "type": "string"
      +          },
      +          "why": {
      +            "description": "One-line reason it matches. With a key.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "brand",
      +          "price",
      +          "currency",
      +          "availability",
      +          "outbound_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "results",
      +    "meta"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (which already establish read-only, idempotent, non-destructive), it discloses that the source item is never returned, that an unknown id yields an error result rather than an empty one, and that an empty list has a distinct meaning. It also surfaces the anonymous cap of 5 with omitted trend data and match reasons, the exact auth header format for a key, and both rate limits — behavioral facts the schema and annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and use cases are front-loaded, followed by return shape, edge-case behavior, then auth and rate limits — a sensible agent-facing order with little wasted wording. The middle sentences run long and pack several distinct facts per clause, which slightly hurts scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with nested filters, the description covers the anchor requirement, what can be refined, what is excluded from results, how errors and empty results differ, and the anonymous-vs-key capability gap. With an output schema present it still briefly names the return shape, which is more than required but not redundant enough to penalize.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, so the baseline is 3, but the description adds intent beyond the field docs by pairing filters.max_price with "cheaper" and filters.availability with "in stock", clarifying these are post-anchor refinements rather than independent search criteria. It does not explain the interaction of limit with the anonymous cap beyond what the limit field already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find alternatives to one item (by id from an earlier result)" names a specific verb and resource, and the clause "pieces close in style, the same product type first" defines the ranking basis, which genuinely separates it from search/complete_the_look. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the id-only input.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete trigger phrases ("something like this but cheaper", "but in stock", "a different color") tied to the corresponding filters, so an agent knows the situations this tool serves. It offers no explicit when-not guidance and never names search or complete_the_look as the alternative for query-based or outfit-based needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources