Steam MCP

Overview Schema Source Related Servers Discussions Admin

steam_get_user_game_stats

Read-only

Retrieve a user's in-game statistics (kills, wins, distance) for a specific Steam game using its app ID, with optional SteamID and language settings.

Instructions

Get a user's in-game STATS for a specific game (kills, wins, distance, etc.).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.18.0Sep 24, 2026

removedInput schema / $defs / PlayerGameInput

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "appid": {
-      "description": "Steam application (game) ID, e.g. 730 for CS2, 570 for Dota 2.",
-      "minimum": 1,
-      "title": "Appid",
-      "type": "integer"
-    },
-    "language": {
-      "default": "english",
-      "description": "Steam language name for localized text (achievement names, etc.), e.g. 'english', 'french', 'german', 'schinese'. Not ISO codes.",
-      "maxLength": 32,
-      "minLength": 2,
-      "title": "Language",
-      "type": "string"
-    },
-    "response_format": {
-      "$ref": "#/$defs/ResponseFormat",
-      "default": "markdown",
-      "description": "'markdown' for human-readable, 'json' for machine-readable."
-    },
-    "steamid": {
-      "anyOf": [
-        {
-          "maxLength": 200,
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "SteamID64 (17 digits), vanity name, or full profile URL (e.g. '76561197960287930', 'gabelogannewell'). Omit to use the configured STEAM_USER (your own Steam name), if set.",
-      "title": "Steamid"
-    }
-  },
-  "required": [
-    "appid"
-  ],
-  "title": "PlayerGameInput",
-  "type": "object"
-}

removedInput schema / $defs / ResponseFormat

Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}

addedInput schema / $defs / UserGameStatsInput

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "appid": {
+      "description": "Steam application (game) ID, e.g. 730 for CS2, 570 for Dota 2.",
+      "minimum": 1,
+      "type": "integer"
+    },
+    "language": {
+      "default": "english",
+      "description": "Steam language name for localized text (achievement names, etc.), e.g. 'english', 'french', 'german', 'schinese'. Not ISO codes.",
+      "maxLength": 32,
+      "minLength": 2,
+      "type": "string"
+    },
+    "limit": {
+      "default": 100,
+      "description": "Max stats to list (1-500); stat_count always covers all of them.",
+      "maximum": 500,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "response_format": {
+      "default": "markdown",
+      "description": "'markdown' for human-readable, 'json' for machine-readable.",
+      "enum": [
+        "markdown",
+        "json"
+      ],
+      "type": "string"
+    },
+    "steamid": {
+      "anyOf": [
+        {
+          "maxLength": 200,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "SteamID64 (17 digits), vanity name, or full profile URL (e.g. '76561197960287930', 'gabelogannewell'). Omit to use the configured STEAM_USER (your own Steam name), if set."
+    }
+  },
+  "required": [
+    "appid"
+  ],
+  "type": "object"
+}

changedInput schema / properties / params / $ref

Previous value: -"#/$defs/PlayerGameInput"New value: +"#/$defs/UserGameStatsInput"

removedInput schema / title

Removed value: -"steam_get_user_game_statsArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_user_game_statsOutput",
-  "type": "object"
-}New value: +null

First observedv1.14.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already covers safety, so the bar is lower. The description adds a little context by clarifying the nature of the stats ('kills, wins, distance'), but it does not disclose return shape, missing-stat behavior, or any quirks beyond what the annotation and schema already imply.

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?

One tight, front-loaded sentence that states the core operation and gives immediately useful examples. There is no filler or redundant restatement of the tool name.

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?

Given the rich input schema and read-only annotation, the description is almost sufficient for a correct invocation. The main missing piece is explicit routing among the large sibling set, which is already penalized under usage guidelines.

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?

The input schema already documents all parameters with descriptions, defaults, and examples (e.g., appid values, steamid formats, limit bounds), so the description does not need to repeat them. The description adds no extra parameter-level meaning beyond the phrase 'for a specific game,' which maps to appid.

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 clear resource ('a user's in-game STATS'), and a scope ('for a specific game'), with concrete examples like kills, wins, and distance. This is immediately distinguishable from broader player-summary or achievement-oriented sibling tools.

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?

The description gives no guidance on when to use this tool versus sibling alternatives such as steam_get_player_achievements or steam_get_game_schema. It also does not mention that steamid is optional and falls back to a configured user, though that information exists in the schema.

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

Deploy Server

steam_get_user_game_stats

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools