Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

steam_top_sellers

Read-only

Fetch Steam's weekly country-specific top-seller ranking records, including full store-item details. cc selects the country/currency. Use steam_charts_most_played for weekly player peaks, steam_charts_top_releases for new releases, or steam_charts_concurrent for live players.

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_top_sellers"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cc / description
      Added value: +"Country code (ISO) whose weekly sales ranking is returned"
    • addedInput schema / properties / l / description
      Added value: +"Steam store language name"
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are weekly, country-scoped, and include full store-item details, but says nothing about pagination, rate limits, or freshness beyond 'weekly'. Useful but not rich beyond the annotations.

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?

Two sentences with no filler; the core capability is front-loaded and the sibling routing follows immediately. Every clause earns its place.

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?

An output schema exists, so return-value documentation is unnecessary, and the description states enough scope (weekly, country-specific, full item details) to call it correctly. Only the language parameter and pagination behavior remain unaddressed, which is a minor gap.

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 coverage is 100%, so both parameters are already documented. The description clarifies that `cc` selects the country/currency, which is marginally more than the schema's 'Country code (ISO)', but the `l` language parameter is not addressed at all. 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?

Specific verb (Fetch) plus resource (Steam's weekly country-specific top-seller ranking records) and scope (including full store-item details). It is immediately distinguishable from the sibling chart tools, which it names explicitly.

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 names three alternatives (steam_charts_most_played for player peaks, steam_charts_top_releases for new releases, steam_charts_concurrent for live players) and the condition that selects each. Routing is unambiguous.

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

All Crawlora MCP toolsInspect
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