Skip to main content
Glama

find_offers

Product-level offers KlickyBot observed on store pages (schema.org JSON-LD or Shopify JSON): price, currency, stock, URL, checked_at. Match by gtin (UPC/EAN), mpn, or name words (q). Optional zip adds a landed-cost estimate; live=true also returns a live (uncached) Shopify Catalog search for q.

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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
mpnNo
payNokeep only offers from stores whose observed payment methods include this code (any code or alias, e.g. link, ln, card; same codes as /q pay=). Stores with unobserved pay methods are left out. The filter runs before limit, so count, total and items describe the filtered set. pay=link with nothing left returns the one_time_link_card note
zipNo
gtinNo
liveNo
limitNo
domainNo
in_stockNo
max_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pay / description
      Previous value: -"keep only offers from stores whose observed payment methods include this code (any code or alias, e.g. link, ln, card; same codes as /q pay=). Stores with unobserved pay methods are left out. pay=link with nothing left returns the one_time_link_card note"New value: +"keep only offers from stores whose observed payment methods include this code (any code or alias, e.g. link, ln, card; same codes as /q pay=). Stores with unobserved pay methods are left out. The filter runs before limit, so count, total and items describe the filtered set. pay=link with nothing left returns the one_time_link_card note"
  2. Changed1 schema field changed
    • addedInput schema / properties / pay
      Added value: +{
      +  "description": "keep only offers from stores whose observed payment methods include this code (any code or alias, e.g. link, ln, card; same codes as /q pay=). Stores with unobserved pay methods are left out. pay=link with nothing left returns the one_time_link_card note",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: data provenance (schema.org JSON-LD or Shopify JSON), freshness via checked_at, and the cached-vs-live distinction for the Shopify Catalog search. It omits result ordering, default limit/pagination semantics, and whether the call performs a network fetch, which matters for a 10-parameter query 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 tight sentences, front-loaded with what the tool returns before listing match keys and modifiers; almost no filler. Slight density cost from unexplained shorthand ('KlickyBot', bare 'q') but nothing is wasted.

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

Completeness3/5

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

The description usefully enumerates return fields, which partly compensates for the absent output schema, and explains the live/zip modifiers. However, for a 10-parameter tool with no annotations and 10% schema coverage, the undocumented limit/domain/in_stock/max_price parameters and missing pagination behavior leave real gaps.

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 only 10% (pay is the sole documented property), so the description must compensate and does so for five parameters: gtin as UPC/EAN, q as name words, mpn, zip as landed-cost trigger, and live as uncached. The remaining parameters (limit, domain, in_stock, max_price) get no explanation in either the schema or the description, leaving half the surface undocumented.

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?

The description names a concrete resource (product-level offers observed on store pages) and the exact payload returned (price, currency, stock, URL, checked_at), plus the three match keys (gtin, mpn, q). It is clearly a lookup tool, distinguishable in spirit from get_landed_price and find_alternatives, though it never explicitly names those siblings to draw the line.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied through parameter behavior: zip 'adds a landed-cost estimate' and live=true 'also returns a live (uncached) Shopify Catalog search'. There is no explicit statement of when to prefer this over get_landed_price, get_checkout_map, or search_merchants, and no exclusions or prerequisites.

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.