Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Summaries

player_summaries
Read-onlyIdempotent

Fetch public Steam profiles for up to 100 comma-separated SteamID64s in one request; returns persona name, avatar, country, and status for each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
steamidsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "steamids": "76561198000000000,76561198000000001"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "response": {
+      "properties": {
+        "players": {
+          "items": {
+            "properties": {
+              "avatar": {
+                "description": "Avatar URL",
+                "type": "string"
+              },
+              "avatarfull": {
+                "description": "Full avatar URL",
+                "type": "string"
+              },
+              "avatarmedium": {
+                "description": "Medium avatar URL",
+                "type": "string"
+              },
+              "communityvisibilitystate": {
+                "description": "Profile visibility",
+                "type": "number"
+              },
+              "loccityid": {
+                "description": "City ID",
+                "type": "number"
+              },
+              "loccountrycode": {
+                "description": "Country code",
+                "type": "string"
+              },
+              "locstatecode": {
+                "description": "State code",
+                "type": "string"
+              },
+              "personaname": {
+                "description": "Display name",
+                "type": "string"
+              },
+              "personastate": {
+                "description": "Online state",
+                "type": "number"
+              },
+              "personastateflags": {
+                "description": "Persona state flags",
+                "type": "number"
+              },
+              "primaryclanid": {
+                "description": "Primary clan ID",
+                "type": "string"
+              },
+              "profilestate": {
+                "description": "Has public profile",
+                "type": "number"
+              },
+              "profileurl": {
+                "description": "Profile URL",
+                "type": "string"
+              },
+              "realname": {
+                "description": "Real name if public",
+                "type": "string"
+              },
+              "steamid": {
+                "description": "SteamID64",
+                "type": "string"
+              },
+              "timecreated": {
+                "description": "Account creation Unix timestamp",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds meaningful context beyond annotations: the 'public' qualifier for profiles, the batch limit of 100, and the return fields, enriching the behavioral picture without contradicting 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.

Conciseness5/5

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

The description is a single sentence that packs in purpose, constraints, and return values with no redundancy. Every clause adds essential information, making it highly efficient and well-structured.

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

Completeness5/5

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

For a tool with one parameter and an output schema, the description covers all necessary context: what it does, the batch limit, the public nature of data, and the returned fields. Annotations cover the safety profile, and the output schema handles return structure, so no critical gaps remain.

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

Parameters5/5

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

The schema provides only a type of 'string' for steamids with 0% coverage. The description fully compensates by specifying the exact format (comma-separated), the ID type (SteamID64), and the maximum of 100 per request, giving the agent precise guidance on constructing valid input.

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 clearly states the tool fetches public Steam profiles for up to 100 comma-separated SteamID64s in one request, and lists the specific returned fields (persona name, avatar, country, status). This identifies a specific verb and resource, and the batch nature distinguishes it from the singular sibling player_summary.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for batch lookups by specifying 'up to 100 comma-separated SteamID64s in one request', giving clear context for when to use it. However, it does not explicitly contrast with alternatives like player_summary or state when not to use it.

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