Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam app player count

steam_app_players_get
Read-onlyIdempotent

Retrieve the current number of players for a Steam app using its app ID, so you can check live player activity before making game or market decisions.

Instructions

Get how many players a Steam app has right now. Requires appId.

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": {
      "appId": "<appId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_app_players_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesRequired. Steam app id, the number in the store URL, e.g. `570` for Dota 2. A store app URL is also accepted.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's only added behavioral signal is that the value is a live current snapshot rather than an aggregate, which is genuinely useful but thin; nothing is said about rate limits, freshness lag, or what happens for an invalid or delisted appId.

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 short sentences, roughly twenty words, with the core action front-loaded and the requirement trailing it. Nothing is padded or redundant.

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 simple single-value read with no output schema, the description conveys enough: which app, what metric, and that it is real-time. Only the shape of the return (a numeric count versus a player list) is left implicit, which is a minor gap for a tool this simple.

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 appId's format, example ('570' for Dota 2) and URL acceptance are already documented in the schema. The description only restates that appId is required, adding no meaning beyond the schema, so the 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 names a specific verb and resource ('Get how many players a Steam app has'), with the temporal qualifier 'right now' pinning it to a live count. It is distinguishable from siblings like steam_app_reviews_summary_get or steam_app_news_list by resource, though it never names those alternatives explicitly.

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?

'Right now' implies a point-in-time snapshot, which is a weak usage hint. There is no guidance on when to prefer a batch variant such as steam_apps_batch_get for multiple apps, and no exclusions or prerequisites are stated beyond the parameter requirement.

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