Custom Blinds Shop

search_products

Read-only

Legacy discovery, retained for backward compatibility. Prefer search_catalog / lookup_catalog, then get_product. Filters by blind type, colour or maximum dimensions. Returns products with id (not product_id), name, description, features and in-stock colour count. Pass that id as product_id to get_price or configure_product.

Input Schema

Name	Required	Description
`type`	No	Blind category to filter by: roller, venetian, honeycomb, vertical, outdoor
`colour`	No	Colour name to search for (partial match)
`province`	No	Optional. Customer's South African province or city. Garden Route locations get Duncan's direct contact; other locations get the online shop contact.
`max_width_mm`	No	Maximum width in millimetres the product supports
`max_height_mm`	No	Maximum height/drop in millimetres the product supports

Output Schema

Name	Required	Description	Default
`total`	Yes
`contact`	No
`currency`	No
`products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 20, 2026

addedOutput schema / properties / contact

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "email": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "whatsapp": {
+      "type": "string"
+    }
+  },
+  "required": [],
+  "type": "object"
+}

removedOutput schema / properties / contact_name
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / contact_phone
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / currency

Added value: +{
+  "const": "ZAR",
+  "type": "string"
+}

removedOutput schema / properties / note

Removed value: -{
-  "type": "string"
-}

removedOutput schema / properties / products / items / properties / colour_count
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / products / items / properties / colour_count_in_stock
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / products / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / products / items / properties / installation_type
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / products / items / properties / materials

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

addedOutput schema / properties / products / items / properties / product_id
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / products / items / properties / starting_price_zar

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / products / items / properties / suitable_for

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedOutput schema / properties / products / items / required

Previous value: -[
-  "id",
-  "name",
-  "category",
-  "product_url"
-]New value: +[
+  "product_id",
+  "name",
+  "category",
+  "product_url"
+]

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "contact_name": {
+      "type": "string"
+    },
+    "contact_phone": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "products": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "colour_count": {
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "features": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "installation_type": {
+            "type": "string"
+          },
+          "materials": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "product_url": {
+            "type": "string"
+          },
+          "suitable_for": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "product_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "products",
+    "total"
+  ],
+  "type": "object"
+}

First observedMay 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value by disclosing the return shape ('id (not product_id), name, description, features and in-stock colour count') and the crucial id-mapping behaviour for get_price/configure_product. It does not mention pagination, result limits, or what an empty result means, so with an output schema present and annotations covering safety, this lands at solid but not rich.

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 legacy caveat and preferred alternatives front-loaded, then filters, then return shape and handoff. Dense but every clause carries information; only minor cost is that the return-shape sentence packs several facts.

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 read-only search tool with full schema coverage and an output schema, the description covers the remaining gaps an agent would otherwise hit: deprecation status, the correct next tool, and the id-vs-product_id naming trap. Nothing needed to call it correctly is missing.

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 100%, so the schema already documents all five parameters including the province-specific contact behaviour. The description only summarises the filter set (blind type, colour, max dimensions) without adding format or syntax detail, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (search products) plus the filtering dimensions available, and immediately distinguishes itself from siblings search_catalog, lookup_catalog and get_product by naming them as preferred. An agent knows exactly what this tool is and that it is a legacy path.

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

Usage Guidelines5/5

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

Explicit routing: 'Legacy discovery, retained for backward compatibility. Prefer search_catalog / lookup_catalog, then get_product.' It gives both the exclusion (don't prefer this) and the ordered alternative chain, which is exactly the when/when-not guidance an agent needs.

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

All Custom Blinds Shop 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.