Custom Blinds Shop

create_cart

Start the open UCP purchase flow, no auth needed. Creates a cart session and returns a cart_id (24-hour TTL). Optionally seed with pre-configured blind items and customer details. Next step: update_cart to add items, then create_checkout → complete_checkout to mint the payment link.

Input Schema

Name	Required	Description	Default
`items`	No	Optional configured items; all submitted prices are ignored
`customer`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`cart_id`	Yes
`currency`	Yes
`customer`	Yes
`total_zar`	Yes
`created_at`	Yes
`expires_at`	Yes
`item_count`	Yes
`updated_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

removedInput schema / properties / customer / description

Removed value: -"Optional customer details (name, email, phone, address, city)."

addedInput schema / properties / items / items / properties / no_drill

Added value: +{
+  "description": "Optional. true for the no-drill option (tension brackets, inside the frame, max 2000mm wide; 1500mm on 25mm venetians). Adds the R65 no-drill kit per blind. Offered on indoor roller blinds, including value rollers, and 25mm aluminium or aluwood venetians. Dedicated no-drill products already include the kit.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 28, 2026
- addedInput schema / properties / customer / description
```
Added value: +"Optional customer details (name, email, phone, address, city)."
```

Changed5 schema fields changedOct 11, 2026

removedInput schema / properties / customer / description
```
Removed value: -"Optional customer details"
```

addedInput schema / properties / customer / properties

Added value: +{
+  "address": {
+    "type": "string"
+  },
+  "city": {
+    "type": "string"
+  },
+  "email": {
+    "description": "Real customer email, checked before checkout creation",
+    "type": "string"
+  },
+  "name": {
+    "description": "Real customer name, checked before checkout creation",
+    "type": "string"
+  },
+  "phone": {
+    "description": "South African phone number, checked before checkout creation",
+    "type": "string"
+  }
+}

changedInput schema / properties / items / description

Previous value: -"Optional initial items (configured blinds)"New value: +"Optional configured items; all submitted prices are ignored"

addedInput schema / properties / items / items

Added value: +{
+  "properties": {
+    "colour": {
+      "description": "Exact available colour; validate with configure_product before adding",
+      "minLength": 1,
+      "type": "string"
+    },
+    "finish": {
+      "description": "Optional pricing finish for aluminium Venetians",
+      "type": "string"
+    },
+    "height_mm": {
+      "description": "Actual ordered drop in millimetres",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "mount_type": {
+      "description": "Use inside for recess fit or outside for face fix",
+      "minLength": 1,
+      "type": "string"
+    },
+    "product_id": {
+      "description": "product_id returned by search_catalog or lookup_catalog",
+      "type": "string"
+    },
+    "product_name": {
+      "description": "Optional; server resolves the catalogue name",
+      "type": "string"
+    },
+    "quantity": {
+      "description": "Number of blinds; defaults to 1",
+      "type": "number"
+    },
+    "total_price_zar": {
+      "description": "Optional, ignored: server recalculates all totals",
+      "type": "number"
+    },
+    "unit_price_zar": {
+      "description": "Optional, ignored: server recalculates all prices",
+      "type": "number"
+    },
+    "width_mm": {
+      "description": "Actual ordered width in millimetres",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "product_id",
+    "width_mm",
+    "height_mm",
+    "colour",
+    "mount_type"
+  ],
+  "type": "object"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "cart_id": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "currency": {
+      "const": "ZAR",
+      "type": "string"
+    },
+    "customer": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "address": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "city": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "email": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "phone": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "item_count": {
+      "type": "number"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "colour": {
+            "type": "string"
+          },
+          "finish": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "height_mm": {
+            "type": "number"
+          },
+          "mount_type": {
+            "type": "string"
+          },
+          "product_id": {
+            "type": "string"
+          },
+          "product_name": {
+            "type": "string"
+          },
+          "quantity": {
+            "type": "number"
+          },
+          "total_price_zar": {
+            "type": "number"
+          },
+          "unit_price_zar": {
+            "type": "number"
+          },
+          "width_mm": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "product_id",
+          "width_mm",
+          "height_mm",
+          "quantity",
+          "unit_price_zar",
+          "total_price_zar"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_zar": {
+      "type": "number"
+    },
+    "updated_at": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "cart_id",
+    "items",
+    "item_count",
+    "total_zar",
+    "currency",
+    "customer",
+    "created_at",
+    "updated_at",
+    "expires_at"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false / destructiveHint=false, so the write-safety profile is covered structurally. The description adds genuinely new behaviour: no authentication required, the returned cart_id has a 24-hour TTL, and customer details are validated later at checkout. It does not cover idempotency, what happens to a pre-existing open cart, or rate limits, which keeps it below a 5.

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: what it is and its auth posture first, then the returned handle and TTL, then the optional seeding, then the downstream workflow. Nothing is repeated from the schema and every clause carries information.

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?

A create/mutation tool with annotations plus an output schema, so return-value shape needn't be explained — yet the description still flags the cart_id and its TTL. Auth posture and the downstream flow are covered; remaining gaps (reusing an existing cart, whether blind items are validated or rejected) are minor.

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?

With only 50% schema description coverage the description must compensate, and it only says 'Optionally seed with pre-configured blind items and customer details' — it names both top-level parameters but adds no detail on required per-item fields (product_id, width_mm, height_mm, colour, mount_type) beyond what the nested schema documents. The schema itself is rich, so the net gain from the description is small.

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+resource ('Creates a cart session') and its concrete output ('returns a cart_id'). It also positions itself in the purchase flow relative to update_cart, create_checkout and complete_checkout, so the agent can distinguish it from get_cart / cancel_cart siblings without opening a schema.

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

Usage Guidelines4/5

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

The description explicitly gives the ordering ('Next step: update_cart to add items, then create_checkout → complete_checkout') and the precondition that no auth is needed, which is exactly the routing an agent needs. It stops short of a 'when not to use' rule (e.g. reuse an existing cart via get_cart instead of creating another), so it is strong but not exhaustive.

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?