Camden Tools

Get basket promotions

get_cart_promotions

Read-only

Evaluate a prospective basket for a destination country: whether it can be fulfilled, which promotions apply (including free-delivery style offers and free gifts) and the adjusted basket value. Same check the checkout runs.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`has_tax_id`	No	Whether the buyer has a VAT/tax id (business purchase).
`country_code`	Yes	Destination country (ISO alpha-2).

Output Schema

TableJSON Schema

Name	Required	Description
`lines`	Yes
`message`	Yes
`free_gifts`	Yes
`promotions`	Yes
`can_fulfill`	Yes
`basket_value`	Yes
`adjusted_value`	Yes	Basket value after promotions.

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": {
+    "adjusted_value": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Basket value after promotions."
+    },
+    "basket_value": {
+      "type": "number"
+    },
+    "can_fulfill": {
+      "type": "boolean"
+    },
+    "free_gifts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "quantity": {
+            "type": "number"
+          },
+          "sku": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "sku",
+          "quantity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "lines": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "quantity": {
+            "type": "number"
+          },
+          "sku": {
+            "type": "string"
+          },
+          "unit_price": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "sku",
+          "quantity",
+          "unit_price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "promotions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "discount_value": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description",
+          "type",
+          "discount_value"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "can_fulfill",
+    "message",
+    "basket_value",
+    "adjusted_value",
+    "promotions",
+    "free_gifts",
+    "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 this as a read-only, non-destructive operation. The description adds meaningful behavioral context by stating it performs the same evaluation the checkout runs, and by revealing that it covers fulfillment, promotions, free gifts, and adjusted basket value. This goes beyond the structured hints without contradicting them.

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 two sentences long, front-loads the core purpose, and contains no filler. Every clause adds useful information: prospective basket, destination country, fulfillment check, promotion types, adjusted value, and checkout parity.

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 evaluation tool with a full input schema, annotations, and an output schema, the description covers everything an agent needs to decide when and why to call it. It does not need to restate parameter mechanics or return values because the structured fields already provide those details.

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 the schema already documents every parameter, including country_code, items, locale, and has_tax_id. The description adds general context about evaluating a prospective basket, but it does not add parameter-specific meaning beyond what the schema already provides.

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 names a specific verb ('Evaluate') and a precise resource ('a prospective basket for a destination country'), and it enumerates the concrete outputs: fulfillment status, applicable promotions, free-delivery offers, free gifts, and adjusted basket value. It also distinguishes itself from product-level tools by scoping to the whole basket and noting it is 'the same check the checkout runs.'

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?

The description clearly establishes when to use the tool: to evaluate a prospective basket against a destination country and see fulfillment plus promotions. It does not explicitly name alternatives or state when not to use it, but the basket-level framing and 'same check the checkout runs' provide strong contextual guidance.

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?