Skip to main content
Glama

ShelfXray quick-commerce shelf data

Brand shelf snapshot by platform and city

brand_shelf_snapshot
Read-onlyIdempotent

For one brand, shows how it appeared on the Blinkit / Zepto / Swiggy Instamart shelf in Bengaluru and Delhi NCR: stores present, coverage %, best and lowest rank seen, and sponsored slots owned, per search keyword. Cached data with read dates. Only top-8 brands per search are recorded.

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": {
      "brand": "<brand>"
    },
    "name": "brand_shelf_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional. One of: Bengaluru, Delhi NCR.
brandYesBrand name, e.g. "Cetaphil", "Blue Tokai", "Yoga Bar". Case-insensitive; partial names match sub-brands (e.g. "Nescafe").
limitNoMax rows returned (default 25).
keywordNoOptional. A searched keyword, one of: baby lotion, baby wash, baby wipes, coffee powder, cold brew coffee, energy bar, granola bar, instant coffee, protein bar.
categoryNoOptional. One of: Baby care, Coffee, Protein & energy bars.
platformNoOptional. One of: Blinkit, Swiggy Instamart, Zepto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real context: results come from cached data with visible read dates, and coverage is capped at the top-8 brands per search. It stops short of describing row-level behavior or how missing stores are represented.

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?

Three short sentences, front-loaded with what the tool returns, followed by two caveats that each carry information an agent needs (cache freshness, top-8 truncation). No filler or restatement of the title.

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?

With no output schema, the description usefully enumerates the returned fields (stores present, coverage %, best/lowest rank, sponsored slots owned) plus the caching and truncation caveats. Combined with 100% schema coverage and clear annotations, an agent has everything needed to call this correctly.

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 coverage is 100%, so the schema already documents all six parameters including allowed city, platform, category, and keyword values. The description reinforces the platform and city scope but adds no syntax, default, or interaction detail beyond the schema, so the baseline 3 applies.

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 resource (one brand's shelf presence) with explicit scope: platforms Blinkit/Zepto/Swiggy Instamart, cities Bengaluru and Delhi NCR, per search keyword. The enumerated outputs (stores present, coverage %, best/lowest rank, sponsored slots owned) make it distinguishable from siblings like category_benchmark and search_rank_summary without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied by the brand-scoped, per-keyword framing, and the 'Only top-8 brands per search are recorded' caveat tells the agent when results will be truncated. However, it never states when to prefer this over search_rank_summary or sponsored_slot_leaders, nor any prerequisite/eligibility conditions.

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