Skip to main content
Glama

Used golf club deals below the usual price

find_used_deals
Read-onlyIdempotent

Use when someone wants to buy a used golf club and asks for deals, bargains or listings for sale, for one club (e.g. "deals on a used TaylorMade P790 iron set", "cheap Vokey SM9") or a club type (e.g. "used driver deals under $200"). Takes a club as the person said it or a club type, and an optional budget in US dollars. Returns up to 5 live eBay listings priced below what that club usually sells for (its median completed-sale price), with title, condition, price before shipping, the usual price and the gap, whether it is a great or good deal, the date it was last checked, and a link for each. Give each link exactly as returned (it counts the click and goes on to the eBay listing) and never build eBay links yourself; include the disclosure that Golf Club Index may earn a commission. For what a club is worth, use golf_used_value instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_used_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubNoThe club as the user said it, e.g. 'taylormade p790 irons'. Give this or category.
categoryNoClub type when no club is named: driver, fairway wood, hybrid, iron, wedge or putter
max_priceNoOptional budget in US dollars, e.g. 200

Output Schema

NameRequiredDescriptionDefault
clubNo
as_ofNo
countNo
dealsNo
foundYes
queryNo
reasonNo
nearestNo
acceptedNo
categoryNo
page_urlNo
max_priceNo
disclosureYes
data_sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that: results are capped at 5 live listings from eBay, benchmarked against median completed-sale price, and carry per-listing fields including last-checked date. It also discloses operational obligations the annotations cannot convey — links must be passed through verbatim because they track clicks, agents must never construct eBay URLs, and a commission disclosure must accompany results.

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?

Front-loaded with the 'Use when' trigger and organized from trigger to inputs to output shape to link handling to the sibling pointer. It is dense and nearly every clause earns its place, though the enumeration of returned fields overlaps with the existing output schema and makes the passage longer than strictly needed.

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

Completeness5/5

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

For a three-parameter read tool with an output schema, the description covers everything an agent needs: trigger conditions, input forms, result cap, price benchmark, and the non-obvious link and disclosure requirements. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by framing club and category as alternatives ('one club ... or a club type') and by stating the budget is in US dollars. It does not add syntax guidance beyond the schema's own examples, so it stops short of 5.

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 and resource: surfaces live eBay listings priced below a club's median completed-sale price. It also distinguishes itself from the sibling golf_used_value by routing valuation questions there, so an agent can tell the two apart 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 Guidelines5/5

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

Explicitly names the trigger ('someone wants to buy a used golf club and asks for deals, bargains or listings for sale') and supplies two concrete example phrasings covering both a named club and a club type. It also states the exclusion — for what a club is worth, use golf_used_value instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources