Camden Tools

Check Website Express eligibility

check_express_eligibility

Read-only

Whole-basket Website Express verdict for a set of product ids and quantities: every line must be eligible (no split shipments).

Input Schema

Name	Required	Description	Default
`items`	Yes	Basket lines as product ids with quantities.
`locale`	No	Storefront locale such as en-GB (default), en-US, de, fr-FR, es-ES, it-IT, nl-NL, pl. Controls product names, slugs and prices.

Output Schema

Name	Required	Description	Default
`lines`	Yes
`enabled`	Yes
`express`	Yes
`basket_eligible`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

changedOutput schema / properties / express / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "available": {
-        "type": "boolean"
-      },
-      "order_by_iso": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "promised_dispatch_date": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "same_day": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "available",
-      "same_day",
-      "order_by_iso",
-      "promised_dispatch_date"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "available": {
+        "type": "boolean"
+      },
+      "order_by_iso": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "promised_dispatch_date": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "same_day": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "available",
+      "same_day",
+      "order_by_iso",
+      "promised_dispatch_date"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / lines / items / properties / reason / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lines / items / properties / reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "basket_eligible": {
+      "type": "boolean"
+    },
+    "enabled": {
+      "type": "boolean"
+    },
+    "express": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "available": {
+              "type": "boolean"
+            },
+            "order_by_iso": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "promised_dispatch_date": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "same_day": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "available",
+            "same_day",
+            "order_by_iso",
+            "promised_dispatch_date"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "lines": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "eligible": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "number"
+          },
+          "reason": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Why a line is not eligible."
+          },
+          "sku": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "sku",
+          "eligible",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "enabled",
+    "basket_eligible",
+    "express",
+    "lines"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the verdict is all-or-nothing, every line must be eligible, and split shipments are not permitted — the single most important semantic an agent needs.

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?

A single dense sentence with the resource and the all-or-nothing constraint front-loaded; nothing is wasted and no filler is present.

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?

An output schema exists so return shape needn't be described, annotations cover safety, and the schema covers inputs. The one gap is that 'Website Express' itself is never explained, but for calling the tool correctly the definition is sufficient.

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 items, id, quantity and locale are already documented in the schema. The description reinforces that items are product ids with quantities but adds no new detail (e.g. the 50-line cap or the locale's effect on pricing/names) beyond 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 verb+resource: a 'Whole-basket Website Express verdict' computed from product ids and quantities. An agent can tell this is an eligibility-check tool, though it does not explicitly contrast itself with siblings like check_shipping_availability or estimate_delivery.

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?

Usage is implied by the name and the 'every line must be eligible' framing, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for per-line or single-product eligibility checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Camden Tools 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?