CheapestInIndia

Compare products

compare_products

Read-only

Compare 2–4 CheapestInIndia products side by side on facts: current price, MRP and discount, store, retailer rating and review count, lowest price ever and in the last 30 days, how far today's price is above its low, and how often the price changes. Use ids from search_products. Highlights the cheapest, the best-rated and the one closest to its lowest price; it does not judge specs.

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": {
      "ids": "<ids>"
    },
    "name": "compare_products"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	2–4 product ids

Output Schema

Name	Required	Description	Default
`rows`	Yes
`cheapestId`	No
`missingIds`	Yes
`bestRatedId`	No
`closestToLowId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The read-only and non-destructive annotations already establish safety. Beyond that, the description discloses useful behavior: what facts are compared, that it highlights the cheapest/best-rated/closest-to-low option, and that it does not judge specs. It does not discuss error cases, but the output schema covers return structure.

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?

The comparison action and count are front-loaded, followed by the comparison dimensions and the ids-source guidance. Despite the long fact list, every phrase adds useful selection or behavioral context, and there is no filler.

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

Completeness5/5

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

For a read-only comparison tool with one fully documented parameter and an output schema, the description supplies the comparison dimensions, highlighting logic, id source, and spec-evaluation limitation. Nothing essential for correct invocation appears to be missing.

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%, and the schema already defines the ids array, its 2–4 item bounds, and the allowed id sources. The description adds only the instruction to use ids from search_products, which is already partly covered by the schema, so this is baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: compare 2–4 CheapestInIndia products side by side. It enumerates the exact comparison facts and explicitly says it does not judge specs, making its scope distinct from search and product-detail tools.

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 tells the agent to use ids from search_products and frames the tool around side-by-side fact comparison for 2–4 products. It does not explicitly say when not to use it or name a direct alternative, but the intended context is clear.

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?