Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam app community hub

steam_app_community_get
Read-onlyIdempotent

Retrieve the players currently in game and active in chat on a Steam community hub by app ID. Use it to gauge live player activity and community engagement for any Steam title.

Instructions

Get the players in game and in chat on a Steam community hub. 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_community_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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no note on whether counts are cached/approximate, no rate-limit or availability caveats, and no indication of the response shape for a tool with no output schema.

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 with zero filler, and the core purpose is front-loaded before the requirement clause. It is efficient, though the second sentence largely duplicates structured schema data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 is the only place to explain what comes back (live player/chat counts? per-hub breakdown?), and it does not. For an open-world read tool with several close siblings, this leaves the agent without enough to confidently select and interpret it.

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 all four parameters (including the analytics and conversation_id plumbing) are already documented in the schema. The description only repeats that appId is required and adds no format or behavioral meaning beyond it, so the baseline of 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 states a concrete verb and resource: it retrieves the in-game and in-chat player counts for a Steam community hub, which is more specific than the generic title. It stops short of distinguishing this from sibling tools such as steam_app_players_get, leaving the boundary ambiguous.

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 when-to-use guidance beyond the bare 'Requires `appId`', which merely restates the schema's required field. Nothing tells the agent when to pick this over steam_app_get or steam_app_players_get, or what conditions make it the right call.

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