Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_player_achievements

Read-only

Retrieve a Steam user's achievement progress for a specific game using its app ID, with optional localized achievement names and Markdown/JSON responses.

Instructions

Get a user's achievement progress for a specific game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.18.0
    • addedInput schema / $defs / PlayerAchievementsInput
      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": 50,
+      "description": "Max locked achievements to list (1-300); the counts always cover all of them.",
+      "maximum": 300,
+      "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"
+}
    • 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"
-}
    • changedInput schema / properties / params / $ref
      Previous value: -"#/$defs/PlayerGameInput"New value: +"#/$defs/PlayerAchievementsInput"
    • removedInput schema / title
      Removed value: -"steam_get_player_achievementsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_player_achievementsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

C2.9/5.0
Behavior2/5

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

The description only restates the read-only nature already captured by the readOnlyHint annotation and contributes no additional behavioral context such as rate limits, auth requirements, response shape, or the limit behavior on locked achievements. It adds no value beyond the annotations.

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?

The description is a single concise sentence that front-loads the verb and object. It contains no fluff, but it is so minimal that it omits useful context. As a concise framing of the core purpose, it is well-structured, though not maximally informative.

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 five parameters and no output schema, the description is insufficiently complete. It doesn't explain what 'achievement progress' encompasses (total, unlocked, locked), how the limit affects the returned list, or how omitted steamid resolves to the configured user. The agent must infer result semantics and edge cases from parameter names and the schema.

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 description does not mention parameters, but the input schema provides detailed descriptions for all five parameters (appid, limit, steamid, language, response_format), including examples, defaults, and format constraints. Since the schema comprehensively documents parameter semantics, the description adds no incremental meaning but the baseline of 3 is appropriate.

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 uses a specific verb and resource ('Get a user's achievement progress for a specific game'), which clearly identifies the tool's function. It implicitly differentiates from siblings like steam_get_user_game_stats or steam_get_global_achievement_percentages by focusing on 'achievement progress' for a single user and game, though it does not explicitly name alternatives.

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 provided on when to use this tool versus alternatives. It does not mention selection criteria, exclusions, or related tools such as steam_get_global_achievement_percentages or steam_get_user_game_stats that might overlap. The agent must infer appropriate usage from the name alone.

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