Skip to main content
Glama

ShelfXray quick-commerce shelf data

Who owns the sponsored slots

sponsored_slot_leaders
Read-onlyIdempotent

Ranks brands by sponsored placements owned (slots, not spend) on the quick-commerce shelf, optionally filtered by platform, city, category or keyword. Answers "who is buying the slots above me?". Cached data.

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

Input Schema

NameRequiredDescriptionDefault
cityNoOptional. One of: Bengaluru, Delhi NCR.
limitNoDefault 10.
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/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is handled. The description adds a genuinely new behavioral trait, 'Cached data', warning the agent that results may be stale, though it does not say how fresh the cache is or how rankings break ties.

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, each earning its place: the ranking definition and scope first, then the filter dimensions, then the analytic framing and the caching caveat. Nothing is padded or repeated.

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?

For a zero-required-parameter, read-only ranking tool with a fully documented schema and no output schema, the description covers scope, metric, filters and data freshness. What is missing is the returned ranking's shape (ordering, per-brand fields) and cache staleness, which are secondary given the schema's completeness.

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% with all five parameters documented including allowed enum values, so the schema carries the parameter burden. The description only restates the filter dimensions at a high level and adds no format, default, or interaction semantics beyond that.

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?

Uses a specific verb ('Ranks') plus resource ('brands by sponsored placements owned') and clarifies the unit of measure with '(slots, not spend)', which prevents a likely misreading. The parenthetical gloss 'who is buying the slots above me?' further pins down what is being ranked.

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?

Implied usage is clear from the question it answers and from the enumerated optional filters (platform, city, category, keyword), so an agent can infer when it applies. However, it never states when not to use it or names any alternative among the siblings such as brand_shelf_snapshot or category_benchmark.

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