Skip to main content
Glama

Look up a product link

lookup_product_by_url
Read-only

Find a product on CheapestInIndia from a retailer link the user pasted (Amazon, Flipkart, Myntra, Ajio, Croma, …) and return its tracked price, price-history summary, variants and similar products. Only products CheapestInIndia already tracks can be found.

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": {
      "url": "<url>"
    },
    "name": "lookup_product_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRetailer product URL, e.g. https://www.amazon.in/dp/B0C…

Output Schema

NameRequiredDescriptionDefault
historyNo
productYes
similarYesSimilar products (other brands or stores)
variantsYesOther sizes/colours of the same product at the same store

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe, closed read operation, so the description's value is in what it adds: an inventory of returned data (tracked price, price-history summary, variants, similar products) and the negative constraint that untracked products cannot be resolved. It does not say whether an untracked URL produces an error or an empty result, which is the one behavior an agent would still want.

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?

Two sentences, both front-loaded with the actionable part: the retrieval statement first, the eligibility caveat second. No filler, no restatement of the name or title.

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 an output schema present, the description needn't enumerate return fields, yet it still previews them; the single parameter is fully covered by the schema. The only real gap is failure semantics for an untracked or unsupported URL, which the tracking-only sentence hints at but does not specify.

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% and the single url parameter is already documented with an example, so the baseline is 3. The description earns an extra point by enumerating supported retailer domains (Amazon, Flipkart, Myntra, Ajio, Croma, …), which tells the agent the input is domain-agnostic rather than Amazon-only.

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?

States a specific verb and resource ('Find a product on CheapestInIndia') and pins the input modality as 'a retailer link the user pasted', which functionally separates it from id-based siblings like get_product. The closing constraint ('Only products CheapestInIndia already tracks can be found') further narrows the scope so an agent knows exactly what this call can and cannot resolve.

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?

The 'link the user pasted' framing gives a clear trigger condition, and the tracking-only limitation tells the agent when this tool will fail. It stops short of naming an alternative (e.g. search_products or get_product for a product name or ID), so routing is implied rather than explicit.

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