Skip to main content
Glama

Vitrine: Trending Fashion, Luxury, Sneakers & Design

Similar brands

similar_brands
Read-onlyIdempotent

Brands close to a given brand (exact name, e.g. 'The Row'): similar style tags, categories, price level and catalog tier, each with a short reason. Optionally only brands with pieces in a category or tier. Unknown brand names return an error; find names with search_brands.

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": {
      "brand": "<brand>"
    },
    "name": "similar_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoOnly return brands with pieces in this catalog tier.
agentNo
brandYesExact brand name from search_brands or any result, e.g. 'The Row'. Case and accents are ignored.
limitNo1 to 20. Anonymous callers get at most 5.
categoryNoOnly return brands with pieces in this category.

Output Schema

NameRequiredDescriptionDefault
metaYes
countYes
anchorNo
resultsYes
query_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the error on unknown brand names, the fact that each result carries a short reason, and the optional narrowing by category or tier.

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

Conciseness5/5

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

Two dense sentences with the core purpose front-loaded, followed by optional refinement, error behavior and the route to name discovery. No sentence is wasted.

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

Completeness4/5

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

With an output schema present, the description needn't explain return shape, and it still flags the 'short reason' field. It covers error cases and filter semantics; the only missing piece is disambiguation from find_similar.

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

Parameters3/5

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

Schema coverage is 80%, so the schema already documents brand, tier, category, limit and agent. The description mostly restates these (exact name, optional category/tier filters) without adding format or semantics beyond what the schema says; baseline 3 applies.

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?

The description names the resource (brands similar to a given brand) and the basis of similarity (style tags, categories, price level, catalog tier) with a concrete example input. It does not, however, distinguish itself from the sibling find_similar, which an agent could easily confuse with this tool.

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?

It gives clear preconditions and routing: brand names must be exact and can be sourced via search_brands, and unknown names error out rather than returning empty. It lacks explicit when-not guidance relative to find_similar and trending_brands, so the agent must infer the boundary.

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