Skip to main content
Glama

PostThisDeal Deal Evidence

Search deals

search_deals
Read-onlyIdempotent

Find current offers PostThisDeal tracks that match a need and budget. Results are the best of the offers PostThisDeal tracks, not every store. Each carries its freshness (confirmed, due, overdue or not independently verified), a status block with the separate facts (verification: independent|merchant|none; freshness; availability; price: matched|changed|variable|unknown; publication), conditions and unknowns. Withdrawn offers are never returned. Give memberships to leave out prices the shopper cannot get.

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": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
queryNoWhat the shopper wants, in words that would appear in a product title.
countryNoISO 3166-1 alpha-2 country of delivery.
categoryNoCategory slug.
currencyNoISO 4217, default USD.
retailerNoRetailer slug, e.g. walmart, target, amazon.
max_priceNoBudget for one item.
fresh_onlyNoOnly offers confirmed inside the freshness window right now (use this before calling a price current).
membershipsNoProgrammes the shopper holds: amazon_prime, walmart_plus, target_circle_360, target_circle_card, costco_member, sams_club, kohls_rewards, student, store_card. Omit if unknown.
verified_onlyNoOnly offers whose price was confirmed at the retailer at some point (the confirmation may be due for a re-check: read freshness.state).

Output Schema

NameRequiredDescriptionDefault
noteNo
totalNo
offersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / fresh_only
      Added value: +{
      +  "description": "Only offers confirmed inside the freshness window right now (use this before calling a price current).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / verified_only / description
      Previous value: -"Only offers whose price was confirmed at the retailer."New value: +"Only offers whose price was confirmed at the retailer at some point (the confirmation may be due for a re-check: read freshness.state)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world search. The description adds meaningful behavior beyond that: results are curated rather than exhaustive, withdrawn offers are never returned, and each result carries freshness and a status block with separate facts. It does not discuss pagination or rate limits, so it is not a 5.

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 description is front-loaded with the core purpose and then adds result semantics. It is fairly dense and repeats 'offers PostThisDeal tracks' in two consecutive sentences, but every sentence carries useful information and there is no major filler.

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?

Given an 11-parameter search tool with an output schema and read-only annotations, the description is largely complete: it explains result scope, withdrawn-offer exclusion, freshness categories, and membership filtering. The main gap is the absence of explicit routing guidance versus sibling tools such as verify_offer or search_comparisons.

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 high at 82%, so the schema already documents most parameter meanings. The description adds useful nuance for memberships by explaining that they exclude prices the shopper cannot get, but it does not add further detail for parameters such as sort, limit, fresh_only, or verified_only beyond what the schema provides.

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 gives a specific verb and resource: find current offers that match a need and budget. It also clarifies that results are a curated subset of tracked offers, not every store. It does not explicitly distinguish this tool from siblings such as search_comparisons or verify_offer, keeping it below 5.

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?

The description implies usage for matching offers to need and budget, and explains that memberships should be supplied to exclude inaccessible prices. However, it gives no explicit when-to-use/when-not-to-use guidance against sibling tools like search_comparisons or verify_offer. The guidance is therefore only implied.

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