Custom Blinds Shop

get_cart

Read-only

Retrieve live cart state by cart_id: full item list, calculated totals in ZAR, and any customer details stored so far. Call after update_cart to confirm changes are correct before proceeding to create_checkout. Cart expires after 24 hours of inactivity.

Input Schema

Name	Required	Description	Default
`cart_id`	Yes

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.

Changed1 schema field changedNov 2, 2026
- removedInput schema / properties / cart_id / description
```
Removed value: -"cart_id returned by create_cart."
```
Changed1 schema field changedOct 28, 2026
- addedInput schema / properties / cart_id / description
```
Added value: +"cart_id returned by create_cart."
```

Changed1 schema field changedOct 11, 2026

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.3/5.0

Behavior4/5

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

readOnlyHint already declares the safety profile, but the description adds real context beyond it: totals are in ZAR, customer details may be partial ('stored so far'), and the cart expires after 24 hours of inactivity, which matters for retry/ordering logic. Return format detail is left to the output schema.

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?

Two sentences, front-loaded with what is returned, then the workflow placement and the expiry constraint. No filler, nothing repeated from the name.

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?

Simple read tool with an output schema that carries return structure and annotations that carry the safety profile. The description covers the remaining gaps an agent needs: scope of the returned data, currency, expiry, and where it fits between update_cart and create_checkout.

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 0% and the single cart_id parameter has no type/format/example documentation anywhere. The description only restates that lookup is 'by cart_id', adding no syntax (e.g. where the id comes from — create_cart output). Adequate for a self-evident identifier, but it does not compensate for the coverage gap.

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?

Specific verb + resource ('Retrieve live cart state by cart_id') plus the exact payload returned: item list, ZAR totals, stored customer details. It is clearly distinguishable from siblings like get_checkout and get_order, which deal with downstream states rather than the live cart.

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?

Explicit sequencing guidance: call after update_cart to verify changes, before create_checkout. That tells the agent where this sits in the workflow. It stops short of naming a when-not-to-use case or an alternative (e.g. use get_checkout once a checkout exists), so not a full 5.

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?