Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_charts_search

Search the steam-charts dataset. Searches daily snapshots of Steam's player-count and sales charts, stored in a search index (one document per chart × country × snapshot × rank) so history accumulates.

Instructions

Search the steam-charts dataset. Searches daily snapshots of Steam's player-count and sales charts, stored in a search index (one document per chart × country × snapshot × rank) so history accumulates. Charts: most_played (weekly peak concurrent), concurrent (live concurrent players), top_sellers (weekly sales; country-specific). With no date the latest snapshot is returned (today's chart); pair app_id with sort=date_desc for an app's rank/players over time. Country is global for the player-count charts or an ISO code (e.g. us) for top_sellers. Sort enum: rank, rank_desc, date_desc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over the game name, max 256 characters
dateNoSnapshot date filter yyyy-MM-dd; defaults to the latest snapshot
pageNoPage number, defaults to 1
sortNoSort enum: rank, rank_desc, date_desc
chartNoChart enum: most_played, concurrent, top_sellers
app_idNoExact Steam app id filter; pair with sort=date_desc for rank/players history
countryNoMarket filter: global (player-count charts) or an ISO country code (top_sellers), max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / chart / enum
      Added value: +[
+  "most_played",
+  "concurrent",
+  "top_sellers"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "rank",
+  "rank_desc",
+  "date_desc"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and largely succeeds: it discloses the billing model (1 credit per record, minimum 2, empty result 2, full page of 100 costs 100), snapshot accumulation behavior, and default-to-latest semantics. Auth/permission and rate-limit behavior beyond billing are not covered, keeping it below 5.

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?

Dense but front-loaded: dataset identity, data model, chart meanings, defaults, history pattern, and billing each appear once with no filler. Slightly long, but every sentence earns its place.

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 an 8-parameter dataset search with no output schema and no annotations, the description covers the essentials: chart/model semantics, date defaulting, sorting intent, country handling, and cost. It is complete enough to call correctly, with only minor gaps around pagination interaction and return fields.

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% (baseline 3), but the description goes beyond the schema by explaining chart semantics (weekly peak vs live concurrent vs weekly sales), that country is global for player-count charts vs an ISO code for top_sellers, and how billing scales with page_size. This is genuine added meaning over the raw enums.

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 ('Search the steam-charts dataset') and explains the underlying data model (one document per chart × country × snapshot × rank). It does not explicitly position itself against nearby siblings like steam_charts_most_played, steam_top_sellers, or datasets_steam_playercounts_search, so it stops short of a 5.

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?

Gives concrete usage patterns: 'with no date the latest snapshot is returned' and 'pair app_id with sort=date_desc for an app's rank/players over time'. Clear context for how to drive the tool, though it names no explicit alternative or when-not-to-use condition, so not a 5.

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

Deploy Server

Other Tools