Fetch the current concurrent-player count for a Steam app by its numeric app ID. Returns live player numbers from the public Steam WebAPI.
Get the current concurrent-player count for a Steam app. Returns the official current concurrent-players count for an app. Credential-free public Steam WebAPI JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| appid | Yes | Numeric Steam app id |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the burden. Mentions it is 'credential-free public Steam WebAPI JSON', which adds useful context about authentication and data format, but does not disclose rate limits, error handling, or response structure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences that front-load the purpose and include essential context (credential-free, public). No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description provides sufficient context (current count, official source) but could mention the expected response format (e.g., JSON object with count).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'appid', which is described as 'Numeric Steam app id'. The description adds no additional meaning beyond 'for a Steam app', so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it gets the current concurrent-player count for a Steam app. The verb 'Get' and specific resource 'current concurrent-player count' differentiate it from sibling tools like steam_charts_concurrent that focus on overall charts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for fetching concurrent players of a single app, but does not explicitly state when to use this tool versus alternatives like steam_charts_concurrent or datasets_steam_playercounts_search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.