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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_code": "<country_code>",
      "items": "<items>"
    },
    "name": "get_cart_promotions"
  }
}

Input 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

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.

Changed8 schema fields changedOct 22, 2026
- removedOutput schema / properties / adjusted_value / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / adjusted_value / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / message / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / message / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / promotions / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / promotions / items / properties / discount_value / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / discount_value / type
```
Added value: +[
+  "number",
+  "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": {
+    "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/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 behavioral context beyond that: it discloses that the tool evaluates fulfillment feasibility, identifies promotions including free-delivery offers and free gifts, and returns an adjusted basket value, matching the checkout check.

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 immediately states what the tool evaluates. Every clause contributes useful information about outcomes and checkout parity, with no redundant or filler text.

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, annotations covering safety, and complete parameter descriptions in the schema, the description provides enough context for an agent to call the tool correctly. It could go slightly further in explaining edge cases or error behavior, but the core evaluation scope is clearly stated.

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 input schema already documents all parameters, including the nested item id and quantity fields. The description adds no additional parameter-level semantics, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Evaluate') and clearly identifies the resource ('a prospective basket') and its scope: fulfillment eligibility, applicable promotions, and adjusted basket value. It also distinguishes this basket-level evaluation from product-level promotion lookup by focusing on a whole basket and stating 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool by explaining that it evaluates a prospective basket and mirrors checkout behavior. However, it does not explicitly mention when not to use it or name alternatives such as get_product_promotions, so the agent must infer the routing from the wording.

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?