Camden Tools

Create a basket link

create_basket_link

Read-onlyIdempotent

Turn product ids and quantities into one link that fills the shopper's basket on camdentools.com. Opening the link makes sure the basket holds at least those quantities (opening it twice does not double them); the shopper reviews the basket and pays at checkout themselves. The result says which lines are out of stock: those cannot be bought, so offer an alternative before sharing the link. Use it to finish a shopping conversation. Ids come from search_products, list_products or get_product.

Input 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

Name	Required	Description
`url`	Yes	Fills the shopper's basket with these lines. Share it unchanged.
`note`	Yes
`lines`	Yes
`unavailable_ids`	Yes	Product ids that were not found.
`out_of_stock_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026
- removedOutput schema / properties / lines / items / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / lines / items / properties / currency / 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": {
+    "lines": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "currency": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "in_stock": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "quantity": {
+            "type": "number"
+          },
+          "sku": {
+            "type": "string"
+          },
+          "stock_level": {
+            "type": "number"
+          },
+          "unit_price": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "sku",
+          "name",
+          "quantity",
+          "unit_price",
+          "currency",
+          "in_stock",
+          "stock_level"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "out_of_stock_ids": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "unavailable_ids": {
+      "description": "Product ids that were not found.",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "url": {
+      "description": "Fills the shopper's basket with these lines. Share it unchanged.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "lines",
+    "unavailable_ids",
+    "out_of_stock_ids",
+    "note"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces the idempotency contract in plain language (\"opening it twice does not double them\"), which is more useful than the hint alone. It also discloses the handoff boundary (the shopper reviews and pays themselves) and that the result flags unbuyable lines — details not present in the annotations. It stops short of covering link lifetime, sharing scope, or failure modes.

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?

Four compact sentences, front-loaded with the core transformation and followed by the behavioral contract, the failure handling, and the id provenance. Every sentence carries information an agent would otherwise have to infer.

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?

Output schema exists, so return values need not be spelled out, and the description picks the one return detail that changes agent behavior (out-of-stock lines). Safety is covered by annotations. Minor gap: nothing about how long a generated link remains valid or whether it must be shared rather than acted on directly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns a notch by naming the three specific sibling tools that supply the id parameter, which is more actionable than the schema's generic \"Product id from search/product tools.\" The locale parameter and quantity/count limits are left entirely to the schema.

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 verb and resource: turning product ids and quantities into a single link that fills a shopper's basket on camdentools.com. It also distinguishes itself from the retrieval siblings by naming where ids come from (search_products, list_products, get_product), so an agent can place it correctly in a workflow.

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?

"Use it to finish a shopping conversation" gives a clear situational trigger, and the out-of-stock instruction (\"offer an alternative before sharing the link\") tells the agent what to do when the preconditions fail. No explicit when-not-to-use or competing alternative is named, but no sibling overlaps this capability.

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?