Custom Blinds Shop

check_colour_stock

Read-only

Verify whether a specific colour is available before configure_product. Returns in_stock boolean, expected_restock_date if out of stock, and up to 5 alternative in-stock colours ordered by similarity. Call this when a customer requests a named colour or when you want to prevent a configure_product failure due to an out-of-stock selection.

Input Schema

Name	Required	Description	Default
`product_id`	Yes
`colour_name`	Yes

Output Schema

Name	Required	Description	Default
`found`	No
`colour`	No
`message`	No
`in_stock`	Yes
`product_id`	No
`expected_restock`	No
`matching_colours`	No
`available_colours`	No
`exact_colour_match`	No
`requires_exact_colour_selection`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- removedInput schema / properties / colour_name / description
```
Removed value: -"Colour name to check, e.g. \"White\"."
```
- removedInput schema / properties / product_id / description
```
Removed value: -"product_id from search_catalog or lookup_catalog."
```
Changed2 schema fields changedOct 28, 2026
- addedInput schema / properties / colour_name / description
```
Added value: +"Colour name to check, e.g. \"White\"."
```
- addedInput schema / properties / product_id / description
```
Added value: +"product_id from search_catalog or lookup_catalog."
```

Changed12 schema fields changedOct 20, 2026

removedOutput schema / properties / alternative_colours

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {
-      "colour_name": {
-        "type": "string"
-      },
-      "in_stock": {
-        "type": "boolean"
-      },
-      "swatch_url": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "colour_name",
-      "in_stock"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / colour
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / colour_name
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / matching_colours / items / properties / colour_name
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / matching_colours / items / properties / expected_restock

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

addedOutput schema / properties / matching_colours / items / properties / finish

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

addedOutput schema / properties / matching_colours / items / properties / hex

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

addedOutput schema / properties / matching_colours / items / properties / material

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

addedOutput schema / properties / matching_colours / items / properties / name
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / matching_colours / items / properties / swatch_url
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / matching_colours / items / required

Previous value: -[
-  "colour_name",
-  "in_stock"
-]New value: +[
+  "name",
+  "in_stock"
+]

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

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "alternative_colours": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "colour_name": {
+            "type": "string"
+          },
+          "in_stock": {
+            "type": "boolean"
+          },
+          "swatch_url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "colour_name",
+          "in_stock"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "available_colours": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "colour_name": {
+      "type": "string"
+    },
+    "exact_colour_match": {
+      "type": "boolean"
+    },
+    "expected_restock": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "in_stock": {
+      "type": "boolean"
+    },
+    "matching_colours": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "colour_name": {
+            "type": "string"
+          },
+          "in_stock": {
+            "type": "boolean"
+          },
+          "swatch_url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "colour_name",
+          "in_stock"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "product_id": {
+      "type": "string"
+    },
+    "requires_exact_colour_selection": {
+      "type": "boolean"
+    },
+    "swatch_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "in_stock"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful behavioral context by explaining the stock check outcome, restock date, and alternatives, though it does not discuss permissions or limits.

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?

The description is front-loaded, efficient, and every sentence supports selection or invocation. It is appropriately sized for a simple two-parameter lookup tool.

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?

The tool has an output schema and readOnly annotation, and the description supplies clear usage context and return behavior. The main gap is that the two required input parameters remain semantically thin in both the schema and description.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It mentions colour availability, but does not explain product_id or give any format or interpretation guidance for colour_name beyond the general idea of a named colour.

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?

The description states a specific verb and resource: verify whether a specific colour is available. It also explicitly names configure_product as the related sibling, making the tool's role easy to distinguish.

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?

It gives clear when-to-use guidance: call it when a customer requests a named colour or to prevent a configure_product failure from an out-of-stock selection. This directly ties usage to an alternative workflow.

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.

Resources

Need Help?