Custom Blinds Shop

lookup_catalog

Read-only

Preferred structured discovery. Filter by category, partial colour name or required supported width/drop in mm. Returns results containing product_id, name, category and product_url, plus total. Width/drop filters check separate maximums, not every combination; confirm the exact pair with get_price.

Input Schema

Name	Required	Description
`colour`	No	Partial colour name to match, e.g. "white".
`category`	No	roller \| venetian \| honeycomb \| vertical \| outdoor
`max_width_mm`	No	Only products that can be made at least this wide, in millimetres. Checked separately from max_height_mm, not as a pair.
`max_height_mm`	No	Only products that can be made at least this high (drop), in millimetres. Checked separately from max_width_mm; confirm the exact pair with get_price.

Output Schema

Name	Required	Description	Default
`total`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedInput schema / properties / colour / description

Added value: +"Partial colour name to match, e.g. \"white\"."

addedInput schema / properties / max_height_mm / description

Added value: +"Only products that can be made at least this high (drop), in millimetres. Checked separately from max_width_mm; confirm the exact pair with get_price."

addedInput schema / properties / max_width_mm / description

Added value: +"Only products that can be made at least this wide, in millimetres. Checked separately from max_height_mm, not as a pair."

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "product_id": {
+            "type": "string"
+          },
+          "product_url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "product_id",
+          "name",
+          "category",
+          "product_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "total"
+  ],
+  "type": "object"
+}

First observedMay 28, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond readOnlyHint=true by disclosing the returned fields (product_id, name, category, product_url, total) and, critically, the non-obvious caveat that width/drop filters apply separate maximums rather than a validated pair. It also routes the agent to get_price for exact-pair confirmation, which prevents a real failure mode.

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?

Three tight sentences, front-loaded with the preference claim, followed by filter coverage and the caveat. Every sentence carries information the agent needs; nothing is redundant.

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?

Output schema exists so return-shape explanation is optional, yet the description still names the key fields and total. Combined with the width/drop caveat and the get_price hand-off, an agent has everything needed to call this correctly.

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 already 100%, so the baseline is 3; the description adds value by clarifying the filter/repeat semantics of width and drop and warning that the pair is not jointly validated. It does not restate enum values or format details, but those are fully covered in the schema.

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 resource (catalog) and its filtering capability by category, partial colour, and width/drop in mm. 'Preferred structured discovery' signals how it differs from the fuzzy search siblings, though it never names search_catalog or search_products.

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?

'Preferred structured discovery' gives a preference cue that implies this is the go-to when filters are known, but it does not state when NOT to use it or name the alternative tools by name. Usage is implied rather than explicit.

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.