Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

datasets_steam_charts_facets

Read-only

Return up to 50 facet buckets with counts for one Steam charts field using the filters from datasets_steam_charts_search. facet accepts chart, country, app_id, or snapshot_date; page and page_size do not change counts; sort is validated but does not change bucket order. A snapshot_date facet without date spans all history. Other facets use the same search date scope: latest snapshot by default, full history for sort=date_desc, and only the requested day when date is supplied. Use datasets_steam_charts_search to find chart records.

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": {
      "facet": "<facet>"
    },
    "name": "datasets_steam_charts_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional full-text query over the game name, max 256 characters.
dateNoOptional snapshot date filter, yyyy-MM-dd. Defaults to the latest available snapshot (today's chart).
pageNoResult page number, 1-based, default 1; page times page_size must not exceed 10000.
sortNoOptional sort order. Allowed values: rank (chart order), rank_desc, date_desc (rank over time). Defaults to rank.
chartNoOptional chart filter. Allowed values: most_played (weekly peak concurrent), concurrent (live concurrent players), top_sellers (weekly sales).
facetYesrequired,Required facet. Allowed values: chart, country, app_id, snapshot_date.
app_idNoOptional exact Steam app id filter; pair with sort=date_desc for an app's rank history over time.
countryNoOptional market filter: global for the player-count charts, or an ISO country code (e.g. us) for top_sellers.
page_sizeNoPage size, default 20, max 100; page times page_size must not exceed 10000.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses real behavioral quirks: page/page_size are ignored for counts, sort is validated but does not reorder buckets, and a snapshot_date facet without a date spans all history. It also spells out the date-scoping rules shared with search, which no structured field conveys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and the ignored-parameter notes, then handles facet-specific edge cases. Dense but nearly every clause carries decision-relevant information; a slightly tighter phrasing of the date-scope sentence would earn a 5.

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?

Given an output schema and safety annotations already present, the description covers everything else an agent needs: what a bucket call returns, which parameters are no-ops, and how date scope behaves per facet. Nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining cross-parameter interaction (facet values accepted, sort/page semantics, snapshot_date with vs. without date). It does not restate every parameter but adds meaning the schema cannot express.

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 verb and resource ('Return up to 50 facet buckets with counts for one Steam charts field') and explicitly ties itself to the sibling search tool whose filters it consumes. An agent can tell this apart from datasets_steam_charts_search and datasets_steam_charts_item without opening schemas.

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

Usage Guidelines5/5

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

Explicitly instructs 'Use datasets_steam_charts_search to find chart records', defining the division of labor between the two tools. It also flags which parameters are inert for this tool (page/page_size do not change counts, sort does not change bucket order), which is exactly the when/when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources