market

find_similar_brands

Given an active catalog brand name or merged alias, find similar brands using brand-profile vectors generated during product indexing. Unknown or ambiguous seeds return no brands. Returns up to 20 brands.

Input Schema

TableJSON Schema

Name	Required	Description
`brand`	Yes	Brand name (case-insensitive), e.g. "Rick Owens".
`limit`	No
`country`	No	Optional shopper location as an ISO-3166-1 alpha-2 country code (e.g. "US", "GB", "DE"). Recorded for analytics and used to improve future offer geo-matching. Omit if unknown — absence preserves current behavior.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`brands`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 13, 2026
- changedInput schema / properties / limit / default
```
Previous value: -8New value: +12
```
Changed1 schema field changedAug 13, 2026
- changedInput schema / properties / limit / default
```
Previous value: -12New value: +8
```

Changed1 schema field changedJun 14, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Optional shopper location as an ISO-3166-1 alpha-2 country code (e.g. \"US\", \"GB\", \"DE\"). Recorded for analytics and used to improve future offer geo-matching. Omit if unknown — absence preserves current behavior.",
+  "pattern": "^[A-Za-z]{2}$",
+  "type": "string"
+}

Changed3 schema fields changedMay 15, 2026

changedInput schema / properties / limit / default
```
Previous value: -10New value: +12
```
changedInput schema / properties / limit / maximum
```
Previous value: -10New value: +20
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "brands": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "about": {
+            "type": "string"
+          },
+          "categories": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "countryOfOrigin": {
+            "type": "string"
+          },
+          "domains": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "genders": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "materials": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "priceTier": {
+            "type": "string"
+          },
+          "shipsFromCountries": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "similarityScore": {
+            "type": "number"
+          },
+          "styles": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "brands"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 4, 2026

changedInput schema / properties / brand / description

Previous value: -"Brand name or brandKey, e.g. \"Rick Owens\" or \"rick owens\"."New value: +"Brand name (case-insensitive), e.g. \"Rick Owens\"."

AddedApr 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, but the description adds the important failure mode that unknown or ambiguous seeds return no brands. It does not explain why readOnlyHint is false for what reads like a lookup tool (the country parameter's analytics/geo-matching note hints at a write), which is an unexplained behavioral trait.

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?

Three tight sentences with the seed requirement front-loaded and no filler. The closing sentence is partially redundant with the schema's limit maximum of 20, which keeps it from being maximally efficient.

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?

An output schema exists, so return structure need not be explained. The description covers the seed requirement, the empty-result case, and the result cap, which is sufficient for a 3-parameter lookup tool; it does not clarify how similarity is ranked or whether country affects results.

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 67%: brand and country are well documented in the schema, while limit is not. The description only says 'up to 20 brands,' which restates the schema's limit maximum=20 rather than adding semantics such as whether similarity is ranked or scored.

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?

States a specific verb+resource (find similar brands) and adds the mechanism (brand-profile vectors generated during product indexing), which distinguishes it from discover_brands and find_similar_products in the sibling set. It is clear what the tool returns, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

The description implies when it is usable by requiring an 'active catalog brand name or merged alias' as the seed, and it warns that unknown or ambiguous seeds return nothing. However, it gives no guidance on when to prefer this over discover_brands or find_similar_products, leaving the routing decision to inference.

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

All market tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.