CheapestInIndia

Biggest recent price drops

top_price_drops

Read-only

Products whose price dropped the most in the last N hours across Indian retailers. Use for 'deals today', 'what got cheaper' or 'price drops on phones'. For a product type, pass category as a plain name (e.g. 'air conditioners', 'mobile phones', 'laptops') in the same call — no need to look up an id first. With a category, products are ranked by the rupee drop; without one, by the percentage drop. Each product's priceChange is the drop in INR (negative). Shown to the user as product cards.

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

Input Schema

Name	Required	Description
`hours`	No	Look-back window in hours (default 24)
`limit`	No	Max products (default 15)
`category`	No	Category name, e.g. 'air conditioners' or 'mobile phones'
`min_price`	No	Ignore products cheaper than this (INR)
`category_id`	No	Category group id from browse_categories (alternative to category)

Output Schema

Name	Required	Description
`hours`	Yes
`category`	No	Category the drops are limited to
`products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds meaningful behavior beyond that: ranking changes based on whether a category is supplied, priceChange is a negative INR drop, and results are shown as product cards.

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 and efficient, moving from the core definition to usage examples and ranking behavior. Most sentences earn their place, though the final note about product cards is less essential for invocation.

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 the output schema and read-only annotations, the description covers the essential call context: what the tool returns conceptually, how ranking works, and how category filtering behaves. It is slightly incomplete on sibling routing and explicit category_id disambiguation.

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 schema already documents the five parameters. The description still adds useful meaning by clarifying that users can pass a plain category name without first looking up an id, and by explaining how category presence changes ranking semantics.

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 clearly identifies the resource and operation: products with the largest recent price drops across Indian retailers, with a configurable look-back window. It is specific and actionable, but it does not explicitly distinguish itself from the sibling brand_price_drops tool.

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?

It gives concrete usage contexts such as 'deals today', 'what got cheaper', and 'price drops on phones', and explains how to pass a category name directly. However, it does not state when to prefer alternatives like brand_price_drops or get_price_history.

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

All CheapestInIndia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?