Skip to main content
Glama

find_deals

Read-onlyIdempotent

Find purchasing options for a specified product, including offers for the same product, alternatives with compatible key attributes, and models with specification upgrades or downgrades. Prices are in USD. query applies only to dupe/ladder. For same_product, use search_products(query) to select a Product first, then pass its product_id without query. Alternative requirements include alternatives joined with or, reference values to keep or not fall below, and specs allowed to get worse. Returns results with product_id, offer_id, title, purchase url, price, currency, seller, coupon and differences, plus summary, comparison and coverage. For dupe/ladder, an optional reference identifies the reference product and price; optional results[].price_delta is the USD difference for the reference quantity (negative is cheaper). Ladder results[].direction is up, down or mixed for specification changes, not price movement. summary reports comparison and returned-offer counts. comparison.product_count, offer_count and retailer_count count distinct products, eligible offers and known retailers whose prices were compared in this call before applicable price filters and the result limit; dupe counts include the reference product. Price excludes tax and shipping and already deducts the single applicable coupon.discount shown; do not deduct it again. The coupon still requires application and its conditions must be met. A null discount is not deducted; a null coupon does not prove no promotion exists. New sellers have null offer_id; use their purchase URL. Returns available purchase quotes only; when no eligible quotes are found, results is empty. Read differences for suitability: matching catalog specs does not guarantee every function is identical. coverage explains the price basis for the requested mode, candidate scope, result limits and unverified attributes. Requirements that cannot be mapped are excluded from filtering and listed in differences and coverage; tell the shopper which conditions were excluded and report the results obtained using the remaining conditions.

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": {
      "product": "<product>"
    },
    "name": "find_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomode=same_product matches the reference listing or standalone description; conflicting variants and international, refurbished, rental or custom listings go in set_aside. Unspecified pack sizes/options may differ. Requirements are matched by search_products at Product level; omit query here. mode=dupe finds alternative models with compatible key attributes; they may be cheaper or more expensive than the reference product. mode=ladder finds models with specification upgrades or downgrades and shows the differences.same_product
queryNoOptional Product requirements for dupe/ladder only. For same_product, send requirements to search_products and pass the selected product_id without query. Unmapped requirements are reported as unverified. Use short feature/value clauses for stated requirements; preserve exact values, ranges, comparison directions and exclusions. Label soft preferences as preferred. Include an absolute USD budget, a cheaper-than-reference requirement, a request to keep a reference value ("keep the capacity") or not fall below it ("battery life no worse"), or permission for a spec to get worse ("capacity may be smaller") only when the shopper asks; otherwise do not infer them. State accepted alternatives with "or"; requirements they share apply to each. A budget is optional. Keep the reference item in product; do not turn its brand/model into candidate filters unless requested. Leave fact-reporting requests without target values and answer-format instructions out of query; retain them for detail checks and the answer. Do not loosen stated requirements yourself to obtain results; pass on only the shopper's own permission for a spec to get worse. Rating, review-count and order requests are not filters here and are reported as unresolved. Omit query when no extra conditions apply.
productYesOne product URL, ASIN, GTIN, product ID, model number or short description. Pass URLs and IDs alone, without appended requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / product / maxLength
      Added value: +2000
    • addedInput schema / properties / product / minLength
      Added value: +1
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses important behavior: prices exclude tax and shipping, coupon discounts are already deducted, null discounts and null coupons have caveats, new sellers may have null offer_id, and empty results mean no eligible quotes. It also explains differences, coverage, and how unmapped requirements are handled.

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 purpose is front-loaded and the length is largely justified by the tool's complexity and the absence of an output schema. However, the description is a single dense paragraph with some repetition of schema details, so it is helpful but not maximally concise or structurally clean.

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?

Given no output schema, the description supplies the return fields, comparison and coverage semantics, price/coupon rules, null handling, and empty-result behavior. It also explains how excluded requirements should be reported to the shopper, making the definition complete for an agent to call and interpret correctly.

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%, and the schema already documents mode, query, and product in detail, so the baseline is 3. The description reinforces the same_product workflow and dupe/ladder query restriction, but it adds relatively little parameter-level meaning beyond what the structured schema already provides.

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?

The first sentence states a specific verb and resource: finding purchasing options for a product, including same-product offers, compatible alternatives, and specification ladders. It also distinguishes the modes and the same_product workflow from search_products, so an agent can tell what this tool is for and how it differs from siblings.

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?

The description explicitly routes same_product users to search_products(query) first, then to pass product_id without query, while query is reserved for dupe/ladder. It also explains when to include budget, reference-value constraints, or permission for specs to get worse, and when not to infer them.

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