Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_charts_most_played

Track Steam's most popular games weekly. Retrieve the ranked chart showing top titles by peak concurrent players over the last seven days.

Instructions

Get Steam's weekly most-played games chart. Returns Steam's weekly most-played chart: the top games ranked by peak concurrent players over the last week (rank, appid, previous-week rank, peak players). By default each row is enriched with the game name and review summary; pass enrich=false for the raw ranked app ids only.

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

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does reasonably well: it discloses the return shape (rank, appid, previous-week rank, peak players) and the default enrichment behavior. It omits any note on auth, rate limits, or freshness/lag of the weekly data, but for a read-only chart endpoint this is solid disclosure.

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?

Two sentences, purpose front-loaded, with no wasted tail. The opening of the second sentence ('Returns Steam's weekly most-played chart') partially restates the first sentence, a minor redundancy that keeps it from a 5.

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?

With no output schema, the description compensates by enumerating the returned fields, and all three optional parameters are covered. For a simple read-only chart tool it is essentially complete, lacking only freshness/permission notes.

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 baseline is 3, but the description adds meaning the schema does not: it states enrich defaults to true and that enrich=false yields raw ranked app ids only. It adds nothing new for l and cc beyond the schema's own descriptions, keeping it from a 5.

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 ('Get Steam's weekly most-played games chart') and pins down the exact ranking criterion (top games by peak concurrent players over the last week) plus the returned fields. That scope implicitly separates it from siblings like steam_charts_concurrent and steam_charts_top_releases without opening a schema.

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

Usage Guidelines3/5

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

It gives a usable usage hint for one parameter ('pass enrich=false for the raw ranked app ids only'), but offers no when-to-use/when-not guidance relative to the other Steam chart tools. Usage is implied through the scope description rather than stated.

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