Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Stats

player_stats
Read-onlyIdempotent

User stats for a game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "playerstats": {
+      "properties": {
+        "achievements": {
+          "items": {
+            "properties": {
+              "achieved": {
+                "description": "Whether unlocked",
+                "type": "number"
+              },
+              "name": {
+                "description": "Achievement name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "gameName": {
+          "description": "Game name",
+          "type": "string"
+        },
+        "stats": {
+          "items": {
+            "properties": {
+              "name": {
+                "description": "Stat name",
+                "type": "string"
+              },
+              "value": {
+                "description": "Stat value",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. However, the description adds nothing about rate limits, required auth, or what data is returned; it's a bare statement with no behavioral context beyond what annotations already provide.

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 sentence, but it doesn't earn its place as it provides minimal information. This is under-specification, not effective conciseness, since the sentence adds little value beyond the tool name.

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?

Even though an output schema exists, the description fails to orient the agent about what 'stats' means, how it differs from similar tools, and what the expected use case is. For a 2-parameter tool within a rich sibling set, this is incomplete and would require the agent to guess or explore.

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?

Schema coverage is 0%, so the description carries the full burden for explaining steamid and appid. It only says 'for a game,' which weakly hints that appid is the game identifier, but neither parameter is explained beyond its name, leaving unclear semantics.

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 'User stats for a game' is a noun phrase that essentially restates the title 'Player Stats' with synonyms. It lacks a specific verb and doesn't specify what kind of stats are included, making it hard to distinguish from sibling tools like player_achievements or player_summaries.

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

Usage Guidelines1/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. The description does not mention any context, prerequisites, or exclusions, leaving the agent to guess which player-related tool fits the query.

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