Skip to main content
Glama

Search live deals

search_deals
Read-only

Search live, human-reviewed deals by keyword. Matching is token-AND over product name, brand, category, and merchant. Returns up to 5 active deals (best score first) with price, discount, condition, merchant, product URL, and a server-verified human_summary sentence. Zero matches is a normal result for time-scarce inventory; the response then includes a no_match block describing the register_watch alternative.

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": {
      "query": "<query>"
    },
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5).
queryYesSearch keywords — product name, brand, model number, or merchant. Token-AND: every word must match.
categoryNoCategory filter (comma-separated allowed). Watch discovery covers the complete canonical taxonomy; current sourcing coverage is reported separately.
max_price_centsNoOnly deals at or below this price, in cents (e.g. 35000 = $350).
min_discount_pctNoOnly deals with at least this discount percentage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category filter (comma-separated allowed). Currently in scope: electronics."New value: +"Category filter (comma-separated allowed). Watch discovery covers the complete canonical taxonomy; current sourcing coverage is reported separately."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses result count, ordering (best score first), the returned fields, and the important behavioral fact that an empty result is normal and structured rather than an error. Minor inconsistency: it says "up to 5 active deals" while the limit parameter permits up to 10, so the cap is ambiguous.

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?

Three tight sentences, front-loaded with the search verb and matching rule, followed by return shape and then the zero-match behavior. No filler; each sentence contributes selection or invocation information.

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 no output schema, the description correctly takes on the burden of describing the response payload and its ordering, plus the no-match variant. Coverage is strong, with only the up-to-5 versus limit-max-10 cap discrepancy and undefined "human-reviewed" left loose.

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 genuine meaning by specifying that matching is token-AND across product name, brand, category, and merchant — which fields are searchable is not stated in the schema. It does not explain the limit/category/max_price filters, but the schema already carries those.

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?

States a specific verb and resource ("Search live, human-reviewed deals by keyword") and goes further by explaining the matching model (token-AND over product name, brand, category, merchant). An agent can distinguish it from a bulk listing tool like latest_deals by the keyword-driven search framing, though no sibling is named except register_watch in the failure case.

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?

Gives concrete when-to-use-fallback guidance: zero matches is normal for time-scarce inventory and the response carries a no_match block pointing at register_watch. It does not, however, explain when to prefer latest_deals browsing or get_deal for a known item, so the alternative routing is partial rather than complete.

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