Caddence

Get price history

get_price_history

Read-onlyIdempotent

Daily lowest/average UK price for one product over a trailing window, plus summary stats (historical low with date, high, trend direction). Optionally scoped to a variant configuration; if the variant series is too thin the backend falls back to product-level history (see scope field).

Input Schema

Name	Required	Description
`days`	No	Trailing window in days
`flex`	No
`hand`	No	e.g. "RH" or "LH"
`loft`	No
`slug`	No	Alias for product — pass either
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`product`	No	Product slug (preferred, from search results) or numeric product id
`condition`	No

Output Schema

Name	Required	Description	Default
`brand`	Yes
`daily`	Yes
`scope`	Yes
`trend`	Yes
`product`	Yes
`days_tracked`	Yes
`low_in_window`	Yes
`high_in_window`	Yes
`current_min_price`	Yes
`retailers_tracked`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "brand": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "current_min_price": {
+      "anyOf": [
+        {
+          "description": "Price in GBP",
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "daily": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "avg": {
+            "description": "Price in GBP",
+            "type": "number"
+          },
+          "date": {
+            "type": "string"
+          },
+          "min": {
+            "description": "Price in GBP",
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "min",
+          "avg"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "days_tracked": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "high_in_window": {
+      "anyOf": [
+        {
+          "description": "Price in GBP",
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "low_in_window": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "date": {
+              "type": "string"
+            },
+            "price": {
+              "description": "Price in GBP",
+              "type": "number"
+            }
+          },
+          "required": [
+            "price",
+            "date"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "product": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "retailers_tracked": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "trend": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "product",
+    "brand",
+    "current_min_price",
+    "low_in_window",
+    "high_in_window",
+    "trend",
+    "days_tracked",
+    "retailers_tracked",
+    "scope",
+    "daily"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 18, 2026

addedInput schema / properties / slug

Added value: +{
+  "description": "Alias for product — pass either",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "product",
-  "context"
-]New value: +[
+  "context"
+]

First observedAug 17, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent profile, but the description adds genuine behavioral context beyond them: the backend falls back to product-level history when the variant series is too thin, and it points the agent to the scope field to detect this. That is meaningful disclosure for a read tool.

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?

Two dense, front-loaded sentences with no filler; the primary output is stated first and the fallback caveat second. Slightly information-packed but every clause 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?

With an output schema present, return values need not be re-explained, and annotations cover the safety profile. The description covers the main output, variant scoping, and the fallback behavior, leaving only minor param gaps undocumented.

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 63%, so several parameters (flex, loft, condition) are undocumented in both places. The description adds context via 'variant configuration' and 'trailing window', mapping loosely to the variant params and days, but does not fully compensate for the coverage gap.

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+resource ('Daily lowest/average UK price for one product over a trailing window') and enumerates the returned summary stats. It clearly distinguishes itself as a single-product historical tool, though it never names a sibling to contrast against.

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?

The description explains what the tool returns but gives no explicit when-to-use guidance or alternatives. It never says when to reach for this versus get_deal_intelligence or get_product_offers, leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Caddence 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?