Skip to main content
Glama

ShelfXray quick-commerce shelf data

Category benchmark: ad pressure, depth and price

category_benchmark
Read-onlyIdempotent

Benchmarks a category (Coffee, Protein & energy bars, Baby care) by platform and city: average distinct brands per search, results depth, share of store reads showing a sponsored result, sponsored slots held by the top brands, and shelf price range. 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": "category_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional. One of: Bengaluru, Delhi NCR.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely new context with 'Cached data', warning that figures may be stale, plus the full metric inventory that tells the agent what a call actually yields. It does not cover freshness windows or how the aggregates are computed.

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?

A single sentence that front-loads the action and dimensioning before the metric enumeration, with the cached-data caveat trailing cleanly. Every clause carries distinct information; none of the enumerated metrics is redundant padding.

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 usefully enumerates the returned measures, and the annotation set covers the safety profile. The remaining gap is default behavior for the three optional filters, which matters because a zero-required-parameter tool must be callable with an empty argument object.

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% and each parameter already lists its allowed values, so the description only adds the semantic framing that these three are the slicing dimensions. It never says what happens when a filter is omitted (all platforms/cities/categories aggregated?), which is the one behavior an agent most needs to know given all parameters are optional.

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?

States a specific verb and resource ('Benchmarks a category') and enumerates the exact metrics returned (brands per search, results depth, sponsored share, top-brand slot ownership, price range), which is far beyond a restatement of the name. It stops short of distinguishing itself from siblings like sponsored_slot_leaders, whose subject matter overlaps the 'sponsored slots held by the top brands' metric.

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?

No explicit when-to-use, when-not-to-use, or alternative is named; usage is only implied by the metric list and the 'by platform and city' dimensioning. An agent can infer this is the aggregate comparison view rather than a per-brand snapshot, but the routing decision against brand_shelf_snapshot or search_rank_summary is left to inference.

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