Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_top_sellers

Fetch Steam's weekly top-sellers chart for a chosen country, listing each ranked game with price, community tags, reviews, and platforms.

Instructions

Get Steam's weekly top-sellers chart for a country. Returns the store's weekly top-sellers chart for a country, each rank carrying the full store item (name, price, weighted community tags, review summary, platforms). cc selects the country whose sales ranking and currency are returned.

Input Schema

NameRequiredDescriptionDefault
lNoSteam store language name
ccNoCountry code (ISO) whose weekly sales ranking is returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the return shape well: each rank carries the full store item including name, price, weighted community tags, review summary, and platforms. It still omits behavior for the optional params (e.g. what country/language is used when cc or l is omitted) and any pagination or rate-limit note.

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?

Purpose is front-loaded in the first clause and the total length is short. The second sentence's opening ('Returns the store's weekly top-sellers chart for a country') partially restates the first, a minor redundancy rather than a real failure.

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 read-only, two-optional-param chart endpoint with full schema coverage and no output schema, the description supplies the payload anatomy an agent needs to use the result. The main gap is that it never says what happens with default country/language when the optional params are omitted.

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 already 100%, so the baseline is 3, but the description adds genuine meaning for cc by stating that it also determines the returned currency, beyond the schema's 'ISO country code' text. The l parameter is never addressed in the description, which keeps it short of a 5.

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?

The description names a specific verb and resource ('Get Steam's weekly top-sellers chart for a country') and even enumerates the payload fields. It is clear what the tool returns, but it never distinguishes itself from closely named siblings like steam_charts_top_releases, steam_charts_most_played, or steam_charts_concurrent, so an agent must infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative sibling is named. The chart context ('weekly top-sellers') only weakly implies usage, leaving the agent to guess between this and the other steam_charts_* tools.

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