Camden Tools

Get Website Express status

get_express_delivery_status

Read-only

Whether Website Express (free same-working-day dispatch for eligible UK orders) is available right now, the order-by cutoff and the promised dispatch date.

Input Schema

Name	Required	Description	Default
`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
`cutoff`	Yes
`enabled`	Yes
`order_by_iso`	Yes
`available_now`	Yes
`express_products_url`	Yes
`promised_dispatch_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 22, 2026

removedOutput schema / properties / cutoff / anyOf

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

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

removedOutput schema / properties / order_by_iso / anyOf

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

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

removedOutput schema / properties / promised_dispatch_date / anyOf

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

addedOutput schema / properties / promised_dispatch_date / 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": {
+    "available_now": {
+      "type": "boolean"
+    },
+    "cutoff": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "enabled": {
+      "type": "boolean"
+    },
+    "express_products_url": {
+      "type": "string"
+    },
+    "order_by_iso": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "promised_dispatch_date": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "enabled",
+    "available_now",
+    "cutoff",
+    "order_by_iso",
+    "promised_dispatch_date",
+    "express_products_url"
+  ],
+  "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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful domain-specific behavior beyond annotations: it clarifies that this is a free same-working-day dispatch for eligible UK orders, and that the response includes the order-by cutoff and promised dispatch date. It does not describe caching or update frequency, but that is a minor gap given the rich annotation coverage.

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?

The description is a single, front-loaded sentence that packs the key concepts—availability, cutoff, and dispatch date—with no wasted words. It is appropriately sized for an agent to parse quickly.

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?

With an output schema present, the description need not explain return values, and it does well to enumerate what status information is provided. The only missing piece is explicit routing guidance relative to sibling tools, but for a read-only status check the description is otherwise complete.

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 100%, and the single optional locale parameter is fully documented in the schema. The description adds no further meaning about the locale parameter, so the baseline score of 3 is appropriate.

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?

The description clearly states the resource (Website Express availability) and enumerates the specific outputs: current availability, order-by cutoff, and promised dispatch date. It does not, however, explicitly differentiate itself from sibling tools like check_express_eligibility or check_shipping_availability.

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 phrases like 'available right now' and 'order-by cutoff', suggesting a live status check. But there is no explicit guidance on when to use this tool versus check_express_eligibility or estimate_delivery, nor any stated exclusions.

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?