Camden Tools

Get prices for a country

get_prices_for_country

Read-only

Country-specific pricing for a set of products (the checkout applies the destination country's currency and pricing). Returns unit, sale and final prices plus the subtotal.

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": {
      "shipping_country": "<shipping_country>",
      "items": "<items>"
    },
    "name": "get_prices_for_country"
  }
}

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

Output Schema

Name	Required	Description
`items`	Yes
`currency`	Yes
`subtotal`	Yes
`fallback_used`	Yes	No prices for this country: another country's were used.
`pricing_country`	Yes
`shipping_country`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 22, 2026
- removedOutput schema / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / final_price / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / final_price / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / sale_price / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / sale_price / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / unit_price / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / unit_price / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / pricing_country / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / pricing_country / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / subtotal / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / subtotal / 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": {
+    "currency": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "fallback_used": {
+      "description": "No prices for this country: another country's were used.",
+      "type": "boolean"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "final_price": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "number"
+          },
+          "quantity": {
+            "type": "number"
+          },
+          "sale_price": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "unit_price": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "quantity",
+          "unit_price",
+          "sale_price",
+          "final_price"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pricing_country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "shipping_country": {
+      "type": "string"
+    },
+    "subtotal": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "shipping_country",
+    "pricing_country",
+    "currency",
+    "fallback_used",
+    "items",
+    "subtotal"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A3.5/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 safety and world-access profile are covered. The description adds that prices are currency-dependent on destination country and enumerates the price tiers returned, but says nothing about how locale interacts with country or about caching/staleness of pricing.

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?

A single tightly written sentence with the core purpose front-loaded. The trailing parenthetical about checkout currency overlaps with 'Country-specific pricing' but is brief enough not to be wasteful.

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?

Low-complexity read tool: 3 parameters at full schema coverage, an output schema present, and annotations carrying the safety profile. The description covers scope and return shape adequately; only the interaction between locale and currency (both affect prices per the schema) is left unremarked.

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%, with locale, shipping_country and nested items/quantity all documented in the schema itself. The description only echoes the country and product-set concepts, adding no syntax or semantics beyond what structured fields supply, so 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?

States a specific verb and resource ('Country-specific pricing for a set of products') and clarifies the scope: destination country drives currency and pricing. No sibling tool in the list computes per-country basket pricing, so it is distinguishable by inference, though no sibling is named explicitly.

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?

No explicit when-to-use or when-not-to-use guidance and no named alternatives (e.g. get_product for single-product detail, get_product_promotions for deals). The parenthetical about the checkout applying destination-country pricing implies the intended context without stating it as a rule.

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?