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

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

Name	Required	Description	Default
`brands`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
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.5/5.0

Behavior3/5

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

Adds real context beyond the annotations: similarity is vector-based, seeds must be active or merged aliases, failed seeds return an empty set, and output is capped. But the annotations declare readOnlyHint=false for what is plainly a read-only lookup, and the description does nothing to clarify that no state is changed (unlike the country parameter, which the schema admits is recorded for analytics). That leaves a genuine ambiguity an agent cannot resolve from either source.

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 short sentences, front-loaded with the verb and mechanism, then the edge case, then the result size. No filler or repetition, though 'Returns up to 20 brands' partially duplicates the schema's limit maximum of 20.

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 needn't be explained, and the description covers seed validity, empty-result behavior, and result volume. The one omission for a lookup tool of this shape is whether results are similarity-ranked, which determines how an agent should present them.

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%, so the schema already documents brand and country. The description adds meaning for the brand parameter (must be an active catalog brand or merged alias) and echoes the 20-result cap that bounds limit. It says nothing about how limit interacts with the default of 12 or about ranking/ordering of results.

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 and resource ('find similar brands') plus the mechanism ('brand-profile vectors generated during product indexing'), which cleanly separates it from find_similar_products and discover_brands by resource. It also constrains the seed to an 'active catalog brand name or merged alias'. Sibling tools are not named explicitly, so it falls just short of a 5.

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?

Gives an implicit usage rule that unknown or ambiguous seeds return no brands, which helps an agent predict failure. However, it never says when to prefer this over discover_brands (broad discovery) or find_similar_products (item-level similarity), so the alternative selection is left 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.