Skip to main content
Glama

Camden Tools

by com.camdentools
OverviewDiscussionsAdmin

Estimate delivery

estimate_delivery
Read-only

Delivery services, charges and transit times for a basket to a destination (country plus postcode/ZIP and city). This is an estimate using placeholder contact details; exact rates are confirmed at checkout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoDestination city.
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.
postcodeNoDestination postcode / ZIP.
country_codeYesISO 3166-1 alpha-2 country code, e.g. GB, IE, DE, US.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
ratesYes
country_codeYes
ddp_includedYesDuties and taxes are prepaid (DDP) in the charges.

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": {
+    "country_code": {
+      "type": "string"
+    },
+    "ddp_included": {
+      "description": "Duties and taxes are prepaid (DDP) in the charges.",
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "rates": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "currency": {
+            "type": "string"
+          },
+          "estimated_transit_days": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "express_dispatch": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Website Express same-day dispatch applies to this rate."
+          },
+          "insured": {
+            "type": "boolean"
+          },
+          "service_code": {
+            "type": "string"
+          },
+          "service_name": {
+            "type": "string"
+          },
+          "total_charges": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "service_code",
+          "service_name",
+          "total_charges",
+          "currency",
+          "estimated_transit_days",
+          "insured",
+          "express_dispatch"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "country_code",
+    "ddp_included",
+    "rates",
+    "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?

Annotations already declare readOnlyHint and destructiveHint, so the tool is safe and non-mutating. The description adds valuable context: it uses placeholder contact details and is an estimate, which is beyond what annotations provide. This prevents the agent from expecting exact rates or real contact information. Given the annotations already cover safety, this is strong added value.

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?

Two sentences, front-loaded with the core purpose, and the second sentence adds a critical caveat (estimate, placeholder) that is relevant. No redundant words. Every sentence earns its place.

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?

The tool is moderately complex (5 params, nested items array), but the input schema is thorough and there is an output schema. The description covers the essentials: what it estimates, the destination components, and the estimate nature. It doesn't mention that it is read-only (but annotations do), and it doesn't detail return format (but output schema exists). Given the richness of structured data, this is complete enough.

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 describes all parameters. The description explicitly mentions 'country plus postcode/ZIP and city', which maps to country_code, postcode, and city, and 'basket' to items. However, it doesn't add details on format, defaults, or locale behavior beyond what the schema already provides. Since the schema is comprehensive, a baseline 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 clearly states the verb ('estimate'), the resource ('delivery'), and the specific scope (services, charges, transit times for a basket to a destination). It distinguishes itself from siblings like check_shipping_availability by focusing on estimation rather than availability, and it sets expectations that this is an estimate, not exact rates. This is specific and actionable.

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 implies when to use this tool: to obtain delivery estimates for a basket to a specific destination. It caveats that exact rates are confirmed at checkout, which helps the agent know not to treat this as final. However, it does not explicitly name alternatives (e.g., check_shipping_availability) or state when not to use it, though the sibling list provides context. Slight deduction for not naming alternatives explicitly.

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