Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Summary

player_summary
Read-onlyIdempotent

Fetch public Steam profile for a single SteamID64: persona name, avatar, profile URL, country, last logoff, visibility status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
steamidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "steamid": "76561198000000000"
+  }
+]
    • 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.2/5.0
Behavior3/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 the 'public' qualifier but does not disclose additional behavioral traits such as rate limits, error behavior, or authentication needs. It does not contradict 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 one sentence, front-loaded with the action and resource, and lists output fields without any filler. Every word earns its place.

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

Completeness4/5

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

The tool is simple with one parameter and an output schema exists, so the description covers the essential return data and use case. It does not address edge cases like invalid IDs or private profiles, but the 'public' qualifier sets expectations. Overall, it is complete enough 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.

Parameters4/5

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

The input schema only defines a required string 'steamid' with no description. The description's 'single SteamID64' tells the agent the type of identifier expected, adding meaning beyond the bare schema. It could be improved by providing format examples or constraints, but it is sufficient for the single-parameter tool.

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 uses the specific verb 'Fetch' and identifies a precise resource: 'public Steam profile for a single SteamID64'. It also enumerates the returned fields, making it easy to distinguish from sibling tools like player_summaries by emphasizing 'single'.

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 clearly implies its use case: fetching a single public profile by SteamID64, which distinguishes it from plural-oriented siblings like player_summaries. However, it does not explicitly state when not to use this tool or mention alternatives by name.

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