Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_current_players

Read-only

Retrieve the live player count for any Steam game using its app ID. Query current concurrency to gauge a game's active audience.

Instructions

Get the number of players currently in-game for a title (live concurrency).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.18.0
    • removedInput schema / $defs / AppOnlyInput / properties / appid / title
      Removed value: -"Appid"
    • removedInput schema / $defs / AppOnlyInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / AppOnlyInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / AppOnlyInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / AppOnlyInput / title
      Removed value: -"AppOnlyInput"
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"steam_get_current_playersArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_current_playersOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds a useful behavioral nuance by emphasizing 'currently in-game' and 'live concurrency', implying a real-time snapshot rather than historical data. It does not disclose failure modes, zero-count behavior, or rate limiting, but given the strong annotation coverage, this is acceptable.

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?

A single, tightly worded sentence carries the core purpose and behavioral qualifier with no filler. All information is front-loaded and easily parsed.

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 tool with one required parameter and a clear return concept, the description plus schema is nearly sufficient to invoke it correctly. The only notable gap is the lack of usage guidance, which is already penalized separately; the return value is adequately implied by 'number of players'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The context signal reports 0% schema description coverage, so the description should compensate for parameter meaning, but it does not. 'For a title' loosely alludes to appid, and response_format is never mentioned, leaving the agent to rely on parameter names and enum values alone.

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 names a specific verb ('Get'), a specific resource ('number of players currently in-game'), and a clear scoping qualifier ('for a title', 'live concurrency'). It is immediately distinguishable from the many sibling steam_get_* tools, none of which target live concurrent 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 Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, nor are any exclusion criteria or sibling comparisons mentioned. The intended use is only implied by the name and the description's phrasing, so an agent has to infer the use-case context.

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