Crawlora MCP

steam_charts_concurrent

Read-only

Fetch the live Steam game leaderboard ranked by current concurrent players, including rank, app ID, current/peak players, and optional name/review enrichment. Set enrich=false for raw ranked records. Use steam_charts_most_played for weekly peaks, steam_players for one app, or datasets_steam_charts_search for stored snapshots.

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

Input Schema

Name	Required	Description
`l`	No	Steam store language name for name enrichment
`cc`	No	Store country code (ISO) for name enrichment
`enrich`	No	Attach game name and review summary to each rank

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.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / cc / description

Added value: +"Store country code (ISO) for name enrichment"

addedInput schema / properties / enrich / description

Added value: +"Attach game name and review summary to each rank"

addedInput schema / properties / l / description

Added value: +"Steam store language name for name enrichment"

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful 'live' vs 'stored snapshot' distinction and the enrich opt-out behavior. However, it doesn't mention whether the leaderboard is paginated, size-bounded, or rate-limited, which is relevant context for an open-world live-fetch tool. Adequate but not rich.

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 sentences, all earning their place: the first covers output shape, the second covers the enrich toggle, the third covers sibling routing. The key routing information is front-loaded. No waste.

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?

Completes the picture for an optional-param, open-world read tool: it clarifies live vs snapshot semantics, the enrichment toggle, and the alternatives. An output schema exists, so return values need not be described. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and all three params are documented in the schema, so the schema does the heavy lifting. The description adds behavioral meaning to enrich (name/review enrichment, raw records when false) that goes slightly beyond the schema's terse text. Baseline 3 is appropriate.

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 states a specific verb and resource ('Fetch the live Steam game leaderboard ranked by current concurrent players') and names the exact fields returned (rank, app ID, current/peak players). It is clearly distinguishable from sibling tools, and explicitly names the alternatives it is not.

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 gives the switching condition for the enrich parameter ('Set enrich=false for raw ranked records') and explicitly routes to three siblings with their distinct use cases: weekly peaks (steam_charts_most_played), single-app tracking (steam_players), and stored snapshots (datasets_steam_charts_search). This is explicit when-to-use guidance.

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?