Skip to main content
Glama

ShelfXray quick-commerce shelf data

Dataset info, coverage and citation

get_dataset_info
Read-onlyIdempotent

Describes the free ShelfXray / Dark Store Index quick-commerce shelf dataset: platforms, cities, categories, searched keywords, read dates, method, limitations and how to cite it. Call first. Cached data, not live.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, closed-world, idempotent, non-destructive behavior. The description adds useful context beyond that: the dataset is free, cached rather than live, and the tool documents method and limitations. It does not detail output format, but no output schema exists and the tool is low-risk.

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?

The description is front-loaded and dense with useful information: dataset identity, covered fields, call ordering, and cache behavior. Every sentence and list item earns its place without filler.

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?

For a simple zero-parameter metadata tool with rich annotations and no output schema, the description is complete. It covers dataset scope, method, limitations, citation, and the important cached-not-live caveat, so an agent can decide to call it first and understand what kind of information it provides.

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?

There are no input parameters, so there is no parameter semantics burden. The zero-parameter baseline is 4, and the description appropriately does not invent parameter details.

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?

The description uses a specific verb, 'Describes', and names the exact resource: the ShelfXray / Dark Store Index quick-commerce shelf dataset. It enumerates the covered metadata areas (platforms, cities, categories, keywords, read dates, method, limitations, citation), which clearly separates this metadata tool from sibling snapshot/benchmark/search tools.

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 instruction 'Call first' gives a clear primary usage condition: invoke this before dataset work. It does not explicitly name alternatives or a when-not condition, but the sequencing guidance is strong for a zero-parameter metadata tool.

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