Camden Tools

Check shipping availability

check_shipping_availability

Read-only

Whether Camden Tools ships to a country, with any restriction message.

Input Schema

Name	Required	Description	Default
`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.
`country_code`	Yes	ISO 3166-1 alpha-2 country code, e.g. GB, IE, DE, US.

Output Schema

Name	Required	Description	Default
`message`	Yes
`available`	Yes
`country_code`	Yes
`deliveries_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026
- removedOutput schema / properties / message / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / message / 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": {
+    "available": {
+      "type": "boolean"
+    },
+    "country_code": {
+      "type": "string"
+    },
+    "deliveries_url": {
+      "type": "string"
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "country_code",
+    "available",
+    "message",
+    "deliveries_url"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that a restriction message may accompany the result, which is mildly useful context, but it does not say what an unsupported/invalid country code yields or how strict the check is.

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?

A single front-loaded sentence with zero filler that states the resource and the accompanying result payload. Nothing redundant and nothing buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description need not explain return structure. However, for a check-style tool the description should at least indicate what to do on an unsupported country or whether the restriction message is the actionable output — the definition stops short of that.

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 both parameters are already documented, including the ISO alpha-2 pattern and the locale options. The description adds nothing about parameters and notably does not explain why locale matters (or that it may be irrelevant) for a shipping check — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description names a specific question the tool answers — whether Camden Tools ships to a given country — which is concrete enough for an agent to select it. It does not distinguish itself from close siblings like check_express_eligibility or estimate_delivery, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives. The description never says to prefer this tool over check_express_eligibility (express options) or estimate_delivery (timing), so the agent must infer the boundary from the name alone.

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?