Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_playercounts_search

Search steam-playercounts dataset. Searches the daily concurrent-player time series for tracked games (one document per appid × day).

Instructions

Search steam-playercounts dataset. Searches the daily concurrent-player time series for tracked games (one document per appid × day). Pair app_id with sort=date_desc for a game's player-count history, or pass date for one day's snapshot. Sort enum: date_desc (default), date_asc, players_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
dateNoSnapshot date filter yyyy-MM-dd
pageNoPage number, defaults to 1
sortNoSort enum: date_desc, date_asc, players_desc
app_idNoExact Steam app id filter
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. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "date_desc",
+  "date_asc",
+  "players_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?

With no annotations provided, the description carries the full burden and does add real behavioral context: a per-record billing model with a minimum of 2 credits, a documented default sort, and the data granularity (one doc per appid × day). It stops short of covering return format, auth, or rate limits, but the pricing disclosure is genuinely useful information not available in the schema.

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 purpose, then usage, then billing in three tight sentences with no filler. Slightly dense, but every sentence carries distinct information an agent needs.

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 5-parameter, fully-documented search tool with no output schema, the description supplies purpose, usage patterns, sort behavior, and cost model. It is largely sufficient; the main omission is any hint of what a result document contains beyond the appid/day granularity.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the interaction between parameters (app_id + sort=date_desc yields history; date yields a snapshot) and by restating which sort value is the default. This clarifies intent rather than merely repeating field descriptions.

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 (search) and resource (steam-playercounts dataset) and describes the underlying data model as a 'daily concurrent-player time series ... one document per appid × day.' This clearly tells an agent what it retrieves, though it does not explicitly differentiate itself from close siblings like datasets_steam_charts_search or datasets_steam_games_search.

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 when-to-use patterns: pair `app_id` with `sort=date_desc` for a game's history, or pass `date` for a single-day snapshot. This is strong task-oriented guidance, but it names no exclusions and does not point to alternative sibling tools for cases this one doesn't cover.

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