Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Steam charts

steam_charts_list
Read-onlyIdempotent

Fetch Steam's most played, daily peak, and weekly top-seller charts by country, week, language, and limit to inspect current player and sales rankings.

Instructions

List Steam's most played, daily peak and weekly top sellers charts. Optional inputs: chart, country, week, language and limit. Returns a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_charts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoWith `top_sellers`: any date in the week you want; Steam snaps it to the week's start. Dates after today are refused. Default: the current week.
chartNo`most_played`: top 100 by players right now; `daily_peak`: top 100 by yesterday's peak players; `top_sellers`: top 100 by sales for a week. Default: `most_played`.
limitNoEntries to return, 1 to 100. Default: 100.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNo`top_sellers` uses this country's chart and prices; `most_played` and `daily_peak` ignore it and return `country` null. Must be a country Steam has a top-sellers chart for. Default: `US`.
languageNoLanguage of the text: a Steam language name or short code such as `german` or `de`. Default: `en`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds only 'Returns a list', which is a minimal return-shape hint, and says nothing about data freshness, the fact that out-of-range dates are refused, or that country is ignored for non-seller charts — all of which live in the schema rather than the description.

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 short sentences, front-loaded with the resource and scope, with no filler. The parameter list is somewhat redundant against a fully documented schema, but it costs little and the definition remains easy to scan.

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 8 parameters, full schema coverage, and annotations in place, the structured data carries most of the load, and the absence of an output schema means 'Returns a list' is thin but tolerable. The description is adequate but does not tell an agent what an entry in the list looks like or how chart selection changes the payload.

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 every parameter (including chart enums, week snapping, country applicability, limit bounds) is already documented in detail. The description only repeats the parameter names and omits the required context/llm_model/conversation_id params, adding no semantics beyond the schema; baseline 3 applies.

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 gives a specific verb and resource ('List Steam's ... charts') and enumerates the three chart variants (most played, daily peak, top sellers), which clearly separates this from app-detail siblings like steam_app_get or steam_app_players_get. It stops short of naming or contrasting any alternative chart/data tool, so it is clear but not fully differentiated.

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?

The only guidance is a flat enumeration of optional inputs; there is no statement of when to pick this over a sibling, when not to use it, or which chart choice suits which question. The conditional logic that actually matters (country/week only affecting top_sellers) is left entirely to the schema.

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