Custom Blinds Shop

get_price

Read-only

Get an exact ZAR price using product_id from search_catalog or lookup_catalog, width_mm and height_mm. Prices include VAT and delivery. Colour selects the bamboo price tier where applicable. A price is not a stock reservation: validate the exact colour and mount with configure_product before creating a cart. Failure can return success:false or a JSON-RPC validation error.

Input Schema

Name	Required	Description
`colour`	No	Optional bamboo colour for colour-specific tier pricing
`finish`	No	Optional finish for aluminium products: Plain, Brushed, Woodgrain
`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.
`quantity`	No	Number of blinds (default 1)
`width_mm`	Yes	Width in millimetres (e.g. 1200)
`height_mm`	Yes	Height/drop in millimetres (e.g. 1500)
`product_id`	Yes	product_id from search_catalog or lookup_catalog (e.g. roller-blockout)

Output Schema

Name	Required	Description	Default
`finish`	No
`limits`	No
`contact`	No
`currency`	Yes
`delivery`	No
`quantity`	Yes
`width_mm`	Yes
`height_mm`	Yes
`lead_time`	No
`next_step`	No
`product_id`	Yes
`product_name`	No
`vat_included`	Yes
`unit_price_zar`	Yes
`total_price_zar`	Yes
`effective_width_mm`	No
`effective_height_mm`	No
`minimum_charge_applied`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 20, 2026

removedOutput schema / oneOf

Removed value: -[
-  {
-    "properties": {
-      "success": {
-        "const": true
-      }
-    },
-    "required": [
-      "product_id",
-      "width_mm",
-      "height_mm",
-      "quantity",
-      "unit_price_zar",
-      "total_price_zar",
-      "currency",
-      "vat_included"
-    ]
-  },
-  {
-    "properties": {
-      "success": {
-        "const": false
-      }
-    },
-    "required": [
-      "message"
-    ]
-  }
-]

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"
-}
```
removedOutput schema / properties / contact_required
```
Removed value: -{
-  "type": "boolean"
-}
```
addedOutput schema / properties / delivery
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / limits

Added value: +{
+  "additionalProperties": true,
+  "properties": {},
+  "required": [],
+  "type": "object"
+}

removedOutput schema / properties / measurement_review_required
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / message

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

addedOutput schema / properties / minimum_charge_applied
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / note

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

addedOutput schema / properties / product_name
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / success

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

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

changedOutput schema / required

Previous value: -[
-  "success"
-]New value: +[
+  "product_id",
+  "width_mm",
+  "height_mm",
+  "quantity",
+  "unit_price_zar",
+  "total_price_zar",
+  "currency",
+  "vat_included"
+]

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / colour

Added value: +{
+  "description": "Optional bamboo colour for colour-specific tier pricing",
+  "type": "string"
+}

changedInput schema / properties / product_id / description

Previous value: -"Product ID from search_products (e.g. roller-blockout, venetian-25mm-aluminium)"New value: +"product_id from search_catalog or lookup_catalog (e.g. roller-blockout)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "oneOf": [
+    {
+      "properties": {
+        "success": {
+          "const": true
+        }
+      },
+      "required": [
+        "product_id",
+        "width_mm",
+        "height_mm",
+        "quantity",
+        "unit_price_zar",
+        "total_price_zar",
+        "currency",
+        "vat_included"
+      ]
+    },
+    {
+      "properties": {
+        "success": {
+          "const": false
+        }
+      },
+      "required": [
+        "message"
+      ]
+    }
+  ],
+  "properties": {
+    "contact_name": {
+      "type": "string"
+    },
+    "contact_phone": {
+      "type": "string"
+    },
+    "contact_required": {
+      "type": "boolean"
+    },
+    "currency": {
+      "const": "ZAR",
+      "type": "string"
+    },
+    "effective_height_mm": {
+      "type": "number"
+    },
+    "effective_width_mm": {
+      "type": "number"
+    },
+    "finish": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "height_mm": {
+      "type": "number"
+    },
+    "lead_time": {
+      "type": "string"
+    },
+    "measurement_review_required": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "product_id": {
+      "type": "string"
+    },
+    "quantity": {
+      "type": "number"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "total_price_zar": {
+      "type": "number"
+    },
+    "unit_price_zar": {
+      "type": "number"
+    },
+    "vat_included": {
+      "type": "boolean"
+    },
+    "whatsapp": {
+      "type": "string"
+    },
+    "width_mm": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedMay 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond readOnlyHint=true, it discloses that prices include VAT and delivery, that colour can shift the bamboo tier, and that failures can surface as success:false or as a JSON-RPC validation error. That is unusually rich behavioral context, though it does not say whether prices are cached or how often tiers change.

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?

Four short sentences, front-loaded with the core action and inputs, followed by pricing semantics, a caveat, and error modes. No sentence is filler and each adds a distinct constraint.

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?

An output schema exists, so return values need not be re-explained. The description covers input provenance, pricing semantics, the mutation boundary (not a reservation), the correct next tool, and the failure surface — everything an agent needs before and after calling it.

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 description coverage is 100%, so all seven parameters are already documented, including the colour-tier and finish semantics. The description echoes the colour-tier behavior and the dimension inputs but adds nothing new about finish, quantity, or the province routing parameter, so it sits at the baseline.

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 definition opens with a specific verb plus resource and defines the exact inputs that determine the answer ('Get an exact ZAR price using product_id from search_catalog or lookup_catalog, width_mm and height_mm'). It is clearly separated from siblings like request_price_match and get_product because this is the deterministic, configured-dimension price lookup.

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 names where product_id must come from (search_catalog or lookup_catalog), states the pre-cart validation step via configure_product, and warns that a price is not a stock reservation. That is explicit when-to-use plus a clearly stated follow-up action instead.

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.