Caddence

Get catalogue stats and valid filter values

get_catalog_stats

Read-onlyIdempotent

Live catalogue totals plus the valid values for search filters (brands, product types, conditions, flexes, hands, price range). Call this before filtered searches if unsure which brand or product_type spellings the catalogue uses.

Input Schema

Name	Required	Description	Default
`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."

Output Schema

Name	Required	Description	Default
`hands`	Yes
`brands`	Yes
`flexes`	No
`retailers`	Yes
`conditions`	Yes
`price_range`	No
`product_types`	Yes
`retailer_count`	Yes
`total_products`	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": {
+    "brands": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "conditions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "flexes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hands": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "price_range": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "max": {
+              "anyOf": [
+                {
+                  "description": "Price in GBP",
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "min": {
+              "anyOf": [
+                {
+                  "description": "Price in GBP",
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [
+            "min",
+            "max"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "product_types": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "retailer_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "retailers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "total_products": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_products",
+    "retailer_count",
+    "retailers",
+    "brands",
+    "product_types",
+    "conditions",
+    "hands"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the data is 'live', and the return includes valid enumerations for each filter facet. It says nothing about auth needs or rate limits, keeping it out of the top band.

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 dense sentences with zero filler. The output contents are front-loaded and the usage trigger follows, which is the right ordering for an agent scanning for a routing decision.

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, the description need not explain the return payload, and annotations carry the safety profile. It covers purpose and timing adequately; only minor gaps remain (e.g. whether stats are scoped per-market/currency) that an agent might wonder about.

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?

There is a single 'context' parameter with 100% schema description coverage, so the schema already documents it fully; per the rubric this is a baseline 3. The description adds no additional meaning about the context parameter, and none is needed.

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+resource up front ('Live catalogue totals plus the valid values for search filters') and enumerates exactly which facets are covered (brands, product types, conditions, flexes, hands, price range). This clearly distinguishes it from the sibling search/price/offer tools, which fetch records rather than catalogue metadata.

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 says to 'call this before filtered searches if unsure which brand or product_type spellings the catalogue uses', giving a concrete trigger condition. It does not name the specific sibling (e.g. search_golf_products) or state when this call is unnecessary, so it stops short of full when/when-not guidance.

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?