Skip to main content
Glama

ShelfXray quick-commerce shelf data

Search rank summary for a keyword

search_rank_summary
Read-onlyIdempotent

For a searched keyword (e.g. "protein bar"), shows per platform and city which brands led the shelf (store coverage, best rank, sponsored slots), how many stores showed an ad, results depth and price spread. Cached data.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_rank_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional. One of: Bengaluru, Delhi NCR.
top_nNoBrands per platform/city (default 8).
keywordYesRequired. One of: baby lotion, baby wash, baby wipes, coffee powder, cold brew coffee, energy bar, granola bar, instant coffee, protein bar.
platformNoOptional. One of: Blinkit, Swiggy Instamart, Zepto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing that results come from cached data, warning the agent about potential staleness, and by enumerating the returned metrics in the absence of an output schema. It does not state cache age, refresh cadence, or what happens when a keyword/platform/city combination has no data.

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?

One front-loaded sentence carries the scope and all output dimensions, followed by a two-word freshness note. There is no filler, no restatement of the title, and no dilution of the key information.

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 no output schema, the description appropriately carries the burden of describing return values, and it does so in concrete terms. Annotations cover the safety profile and the schema fully documents inputs. The remaining gaps are that no-data behavior and the meaning of aggregate fields like 'results depth' and 'price spread' are left unspecified.

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%: each of the four parameters carries its own description with allowed values and defaults. The description reinforces the per-platform and per-city grouping and gives a keyword example ('protein bar') that matches the schema's enum list. It adds no semantics for top_n, city or platform beyond what the schema already states, so baseline 3 applies.

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 states a concrete verb and resource ('shows per platform and city which brands led the shelf') and enumerates the metrics returned: store coverage, best rank, sponsored slots, ad-store counts, results depth and price spread. That is far more specific than a restated title. It stops short of naming how it differs from siblings such as brand_shelf_snapshot or sponsored_slot_leaders, which overlap in subject matter.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, despite siblings covering adjacent territory (brand_shelf_snapshot, sponsored_slot_leaders, category_benchmark). The only contextual hint is 'Cached data', which speaks to freshness rather than selection. An agent must infer the routing decision from the sibling names alone.

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