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

TableJSON 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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the verdict is for the whole basket and fails if any single line is ineligible, and split shipments are disallowed.

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?

One tight sentence front-loads the verb and resource, then clarifies the critical eligibility rule in a parenthetical. There is no filler or repetition of schema content.

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?

The description, rich input schema, output schema, and annotations together give an agent everything needed to select and invoke this tool correctly. Return-value details are covered by the output schema, and safety semantics by annotations.

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%, with clear documentation for items and locale. The description adds the basket-level relationship but does not need to explain parameter details because the schema already carries that weight.

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 operation: a whole-basket Website Express eligibility verdict over a set of product ids and quantities. The qualifier 'every line must be eligible (no split shipments)' adds a precise scope and distinguishes it from shipping-availability and delivery-status siblings.

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?

Provides clear context: use this when a basket-level Website Express eligibility check is needed. It does not explicitly name alternatives or when-not-to-use, but the whole-basket/no-split wording is sufficient to route an agent away from related tools.

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?