Skip to main content
Glama

Camden Tools

by com.camdentools
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesBasket lines as product ids with quantities.
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
urlYesFills the shopper's basket with these lines. Share it unchanged.
noteYes
linesYes
unavailable_idsYesProduct ids that were not found.
out_of_stock_idsYes

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": {
+    "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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With read-only and idempotent hints already present, the description adds concrete details: repeated opening doesn't double quantities, the shopper checks out themselves, and the response flags out-of-stock lines. This clarifies the side effects and limits without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main action and stays compact; all sentences convey useful operational context (idempotency, out-of-stock, sourcing, use case). Slight redundancy in the parenthetical about opening twice could be trimmed, but it is meaningful.

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 create-link tool with full schema, output schema, and safety annotations, this covers the essential agent decisions: when to use it, where to get ids, how idempotency works, and how to handle out-of-stock results. No important behavioral or usage gap remains.

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%, so the schema already documents items and locale fully. The description reinforces that ids originate from product-search tools but adds no new format or constraint beyond the schema, matching the baseline for full schema coverage.

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 deliverable: turning product ids and quantities into a single basket-filling link. It also names the exact domain (camdentools.com), distinguishes the output from simple product lookup, and is clearly distinct from all sibling tools.

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?

Explicitly tells the agent when to use it ('finish a shopping conversation') and where valid ids come from (search_products, list_products, get_product). It also tells the agent to offer alternatives for out-of-stock lines, though it doesn't enumerate when not to use the tool since no direct alternative exists.

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