Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

steam_charts_concurrent

Fetch Steam's live leaderboard of games ranked by concurrent players, including rank, current players, and peak; optionally add names and review summaries.

Instructions

Get Steam's live games-by-concurrent-players leaderboard. Returns the live leaderboard of games ranked by current concurrent players (rank, appid, current concurrent, peak). By default each row is enriched with the game name and review summary; pass enrich=false for raw ranked app ids.

Input Schema

NameRequiredDescriptionDefault
lNoSteam store language name for name enrichment
ccNoStore country code (ISO) for name enrichment
enrichNoAttach game name and review summary to each rank

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden but does add real value: it discloses the default enrichment (name + review summary) and the raw-appid behavior when enrich=false, plus the exact returned fields. It omits scope constraints such as pagination, leaderboard size, region/language effect on results, and rate-limit/auth posture.

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?

Three sentences: purpose, then returned fields, then the enrich toggle — front-loaded and free of filler. It could be tightened slightly, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description does cover the returned fields and default behavior, which is the essential part. It nonetheless leaves out sibling differentiation and any scoping/pagination detail for a leaderboard that is presumably bounded.

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%, so the schema already documents all three parameters, giving a baseline of 3. The description adds the fact that enrichment is on by default and clarifies the enrich=false output shape, but says nothing about how 'l' and 'cc' affect results.

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?

It names a specific verb and resource ('Get Steam's live games-by-concurrent-players leaderboard') and even enumerates the return fields, so the function is unambiguous. However, it never distinguishes itself from the closely related sibling steam_charts_most_played, which an agent could easily confuse with this live-concurrent chart.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and the near-identical sibling steam_charts_most_played is not addressed. The only conditional guidance is about the enrich toggle, which is parameter behavior rather than tool selection.

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