Steam MCP Server

Overview Schema Source Related Servers Discussions Admin

Get current player count

get_current_players

Read-only

Retrieve the live concurrent player count for any Steam game using its appid. Returns the current number of players or an error for invalid appids.

Instructions

Get how many people are playing a game right now (live concurrent player count) by appid. Get the appid from search_games. No API key required. Errors clearly if the appid is unknown/invalid rather than returning a null count.

Input Schema

Name	Required	Description	Default
`appid`	Yes	Steam application id (appid). Get it from search_games.

Output Schema

Name	Required	Description	Default
`appid`	Yes
`player_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.14.0Sep 27, 2026
- removedOutput schema / properties / player_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / player_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
Changed1 schema field changedv0.12.1Jul 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Addedv0.10.2Jul 22, 2026
Removedv0.8.0Jul 17, 2026
First observedv0.1.0Jun 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavior beyond that: no API key required, and clear errors on unknown/invalid appid instead of returning a null count. This is useful operational context.

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?

Three concise sentences, each earning its place: what the tool does, where to get the required parameter, and expected error behavior. Information is front-loaded and there is no fluff.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only tool with a full output schema and annotations covering safety, the description covers the prerequisite, error behavior, and authentication requirement. Nothing essential is missing for correct invocation.

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% and the appid parameter already has a description that says to get it from search_games. The description mostly repeats this, adding only the 'by appid' framing. Baseline 3 is appropriate since the schema carries the semantic weight.

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?

The description clearly states the specific action (get live concurrent player count) and the resource (a game identified by appid). It distinguishes itself from sibling tools like get_items and get_game by focusing on current player counts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent to obtain the appid from search_games, which is a clear prerequisite. It does not name alternatives or exclusions, but none are necessary given the unique purpose of this tool among siblings.

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