Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Current Player Count

current_player_count
Read-onlyIdempotent

Current concurrent players.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "appid": 730
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "response": {
+      "properties": {
+        "player_count": {
+          "description": "Current concurrent players",
+          "type": "number"
+        },
+        "result": {
+          "description": "Result code (1 = success)",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. However, the description adds no behavioral context beyond that, such as what 'current' means, whether it is real-time, or what the response structure looks like. It contributes nothing 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.

Conciseness2/5

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

The description is extremely short, but it is under-specified. It is a fragment, not a sentence, and provides minimal information. While it is concise, the brevity is harmful because it obscures essential details.

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 there is an output schema and annotations, the description lacks any context about what 'current concurrent players' means, how to interpret the appid, or any retrieval behavior. For a simple tool, it might be enough, but the absence of parameter explanation and usage guidance makes it incomplete.

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?

The description does not explain the 'appid' parameter at all. Schema description coverage is 0%, so the description must compensate, but it fails. An agent cannot infer that appid refers to a game/application ID or how it affects the returned player count.

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 'Current concurrent players' is a noun phrase that essentially restates the title 'Current Player Count'. It lacks a verb and does not explicitly state what the tool does (e.g., retrieve, fetch). It gives a vague idea but doesn't distinguish from sibling tools like 'app_details' or 'player_stats'.

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. It does not mention any use cases, exclusions, or related tools. The sibling list is large, but the description provides no context for selection.

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