Skip to main content
Glama

Camden Tools

by com.camdentools
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
localeNoStorefront 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
NameRequiredDescriptionDefault
cutoffYes
enabledYes
order_by_isoYes
available_nowYes
express_products_urlYes
promised_dispatch_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.1/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, covering the safety and real-time nature. The description adds value by specifying the exact outputs (availability, cutoff, dispatch date), which is not present in the annotations. It does not contradict any annotation.

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 conveys the essential information without fluff. It states the core question (availability) and the key outputs (cutoff, dispatch date) efficiently.

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?

For a read-only status tool with one optional parameter, an output schema, and annotations covering safety and open-world behavior, the description is complete. It provides enough context for an agent to understand what the tool does and what it returns, without needing to explain return formats (since the output schema exists).

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?

The schema fully describes the single optional locale parameter (100% coverage), so the description does not need to add further detail. The description makes no mention of locale's effect on the express status, but that is already covered by the schema, and the baseline of 3 applies when the schema does the heavy lifting.

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?

The description clearly states the tool's purpose: to report whether Website Express is currently available, along with the order-by cutoff and promised dispatch date. It uses a specific verb (get) and resource (Website Express status), and it distinguishes from siblings like check_express_eligibility (which checks eligibility for a specific order) and check_shipping_availability (general shipping) by focusing on current availability rather than eligibility or general shipping.

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?

The description implies when to use this tool (to check Website Express availability) but does not explicitly mention when to use alternatives like check_express_eligibility or check_shipping_availability. There is no direct guidance on when not to use it or how it differs from these siblings, so the agent must infer the usage context.

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

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