Crawlora MCP

datasets_steam_playercounts_item

Read-only

Fetch one stored Steam player-count point by the exact app_id and snapshot_date returned by datasets_steam_playercounts_search. Dates use yyyy-MM-dd; absent records return 404. Use datasets_steam_playercounts_search to find player-count history.

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": {
      "app_id": "<app_id>",
      "snapshot_date": "<snapshot_date>"
    },
    "name": "datasets_steam_playercounts_item"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes	Required Steam app id returned by datasets_steam_playercounts_search.
`snapshot_date`	Yes	Required snapshot_date returned by datasets_steam_playercounts_search.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two concrete behaviors beyond that — the yyyy-MM-dd date format and a 404 for absent records — which an agent cannot infer from annotations. It does not discuss payload shape, but an output schema exists to carry that.

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?

Three short sentences, each carrying distinct information: what it returns, the date format plus error behavior, and the retrieval path via the sibling. The core action is front-loaded with no 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 two-key leaf lookup with full schema coverage, annotations, and an output schema, the description covers everything the agent needs: how to obtain valid keys, the exact date format, and what happens when a record 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 both parameters are already documented with their provenance. The description contributes genuinely new detail by specifying the yyyy-MM-dd format for snapshot_date, which the schema leaves as an unformatted string.

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 names a specific verb and resource — 'Fetch one stored Steam player-count point' — and immediately scopes it to the exact app_id + snapshot_date pair. It distinguishes itself from the sibling search tool, which covers history rather than a single point.

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?

It explicitly routes the agent: use datasets_steam_playercounts_search to find player-count history, and call this only with the exact keys that search returned. Both the when and the alternative are stated outright.

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

All Crawlora MCP tools Inspect

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

Need Help?