Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Achievements

player_achievements
Read-onlyIdempotent

Achievements for a game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNo
appidYes
steamidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerstatsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "appid": 730,
+    "steamid": "76561198000000000"
+  },
+  {
+    "appid": 570,
+    "l": "english",
+    "steamid": "76561198000000000"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "playerstats": {
+      "properties": {
+        "achievements": {
+          "items": {
+            "properties": {
+              "achieved": {
+                "description": "Whether unlocked (0 or 1)",
+                "type": "number"
+              },
+              "apiname": {
+                "description": "Achievement API name",
+                "type": "string"
+              },
+              "description": {
+                "description": "Achievement description",
+                "type": "string"
+              },
+              "icon": {
+                "description": "Icon URL",
+                "type": "string"
+              },
+              "icongray": {
+                "description": "Locked icon URL",
+                "type": "string"
+              },
+              "name": {
+                "description": "Achievement display name",
+                "type": "string"
+              },
+              "unlocktime": {
+                "description": "Unix timestamp when unlocked",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "gameName": {
+          "description": "Game name",
+          "type": "string"
+        },
+        "steamID": {
+          "description": "SteamID64",
+          "type": "string"
+        },
+        "success": {
+          "description": "Whether data was retrieved",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

D1.8/5.0
Behavior2/5

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

The description adds no behavioral context; annotations already provide readOnly and idempotent hints. It does not disclose any additional traits such as returning a list, language behavior, or what happens if no achievements exist. However, since annotations cover safety, the description's lack of extra context is somewhat mitigated, but it still fails to describe the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase, but it is under-specified rather than concise. It lacks substance and does not earn its place; it is essentially a title, not a functional description.

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

Completeness1/5

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

Despite the existence of an output schema and annotations, the description is completely inadequate for a tool with two required parameters. It does not explain what data is returned, how to format a call, or any prerequisites, making it insufficient for an agent to invoke correctly.

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

Parameters1/5

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

With 0% schema description coverage, the description must explain the parameters but only says 'Achievements for a game.' It does not define appid, steamid, or l, nor any relationship between them. Examples in schema are not part of the description text, so no parameter meaning is conveyed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Achievements for a game' is a noun phrase that essentially restates the tool name/title without a verb or clear action. It does not specify whether it retrieves, lists, or summarizes achievements, and provides no differentiation from sibling tools like player_stats or player_bans.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention required inputs (steamid, appid) or any context like needing a specific Steam ID. The description offers no explicit or implicit usage scenarios.

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

All Steam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources