Skip to main content
Glama
Deal Radar MCP Server

Deal Radar MCP Server

search_deals

Search products and discounts across e-commerce and quick-commerce platforms to compare deals by pincode and category.

Instructions

Search for products, discounts, and trending deals across e-commerce (Flipkart, Myntra, Amazon) and 10-minute quick-commerce platforms (Blinkit, Zepto, Swiggy Instamart, Flipkart Minutes, Amazon Fresh).

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
limitNoMaximum number of results per store (default: 5)
queryYesProduct name or search keyword (e.g. "milk", "Sony WH-1000XM5", "MacBook Air M2")
storesNoOptional list of store IDs to search in (e.g. ["blinkit", "zepto", "flipkart"]). Defaults to all.
pincodeNo6-digit Indian PIN code to check hyper-local 10-minute quick commerce availability (e.g. "560001", "110001", "400001")
storeCategoryNoFilter stores: "quick_commerce" (Blinkit, Zepto, Instamart...), "ecommerce" (Flipkart, Myntra, Amazon...), or "all"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing about authentication, rate limits, whether results are live or cached, how per-store results are combined, or what happens when a pincode is absent. Listing the covered platforms is scope information, not behavioral disclosure.

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?

A single front-loaded sentence with the verb first and no filler. The long platform enumeration costs some length but is informative for store selection.

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 a fully documented 5-parameter schema and no output schema, the description covers the essential scope (what is searched and where) well enough to call the tool. It omits return-shape and result-mixing details, which is a modest gap for a read-only search with no annotations to compensate.

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%, so every parameter including the storeCategory enum is already documented; baseline 3 applies. The description's mapping of platform names to the ecommerce/quick_commerce split adds only marginal meaning beyond the enum description.

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 concrete verb ("Search") and concrete resources (products, discounts, trending deals), and enumerates the platforms covered, which lets an agent tell it apart from search_flights or track_product. It stops short of naming a near-sibling such as compare_prices, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The description gives no when-to-use, when-not-to-use, or alternative guidance; it only says what the tool searches. An agent must infer from the platform list that this is the discovery entry point and that compare_prices/track_product are the follow-ups.

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