Skip to main content
Glama
Sign In

Caddence

by golf.caddence
OverviewDiscussionsAdmin

Get verified market deals

get_market_deals
Read-onlyIdempotent

Current best-value products across the UK market: largest verified price spreads between retailers (3+ retailers, false-positive filters applied). Good for "what are the best golf deals right now?". Follow up with get_product_offers for purchase links.

Input Schema

NameRequiredDescriptionDefault
limitNo
contextYesExplain 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."
categoryNoProduct type filter, e.g. "driver", "iron_set", "putter"

Output Schema

NameRequiredDescriptionDefault
dealsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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": {
+    "deals": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "brand": {
+            "type": "string"
+          },
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "price_from": {
+            "description": "Price in GBP",
+            "type": "number"
+          },
+          "price_to": {
+            "description": "Price in GBP",
+            "type": "number"
+          },
+          "product_url": {
+            "description": "Absolute URL",
+            "type": "string"
+          },
+          "retailer_count": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "savings_gbp": {
+            "description": "Price in GBP",
+            "type": "number"
+          },
+          "savings_pct": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "brand",
+          "slug",
+          "category",
+          "price_from",
+          "price_to",
+          "savings_gbp",
+          "savings_pct",
+          "retailer_count",
+          "product_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "deals"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real behavioral context by disclosing the deal-selection criteria (3+ retailers, false-positive filters) that determine what appears in the results. It does not mention the result cap (limit max 25) or ranking order, which would have pushed it higher.

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?

The selection criteria and scope lead, with the use-case cue and follow-up guidance trailing in short sentences — no filler. Slightly informal by using a quoted user utterance, 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?

An output schema exists, so return values need no explanation, and the description covers scope, ranking logic, and the natural next step. The main omission is any hint that results are capped/filterable via limit and category, which matters for an agent planning a broad query.

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 67% and the description adds no parameter-level information at all — limit and category are never mentioned, and the product-type filtering implied by category is not acknowledged. Baseline 3 applies because the schema already documents the context parameter thoroughly while the remaining params stay silent in both places.

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 resource (current best-value products) with an explicit ranking basis — largest verified price spreads between 3+ retailers after false-positive filtering — and scopes it to the UK market. It also distinguishes itself from the sibling get_product_offers by naming the follow-up intent, so an agent can route correctly without opening either schema.

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?

"Good for 'what are the best golf deals right now?'" gives a concrete triggering use case, and the follow-up pointer to get_product_offers clarifies what this tool is not for (purchase links). No explicit when-not or prerequisite conditions are stated, so it falls short of a 5.

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

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