Skip to main content
Glama
Sign In

SteamGPT

by net.steamgpt
OverviewDiscussionsAdmin

SteamID resolver

steam_identity
Read-onlyIdempotent

Use when the user gives a vanity name or a steamcommunity.com/id/ link and the steamid64 behind it is needed, or when a resolved identity is needed in every format without profile data: steamid64, SteamID (STEAM_1:0:x), SteamID3 ([U:1:x]), steam hex, vanity, profile URL. Resolution goes through Steam; unresolvable ids return an error result - never a partial guess. Do not use for pure format conversion of a known id (steam_convert is cheaper) or for profile data (steam_profile).

Input Schema

NameRequiredDescriptionDefault
idYesany SteamID format: steamid64 (17 digits), STEAM_1:0:x, STEAM_0:0:x, [U:1:x], hex, steam:hex, a 32-bit account id, a steamcommunity.com link or a vanity name

Output Schema

NameRequiredDescriptionDefault
vanityNocustom URL name when known, otherwise null
steamidNoSTEAM_1:y:z
resolvedNo
steamid3No[U:1:x]
steam_hexNosteamid64 in hexadecimal
steamid64No
profile_urlNosteamcommunity.com/profiles/ link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "profile_url": {
+      "description": "steamcommunity.com/profiles/ link"
+    },
+    "resolved": {
+      "type": "boolean"
+    },
+    "steam_hex": {
+      "description": "steamid64 in hexadecimal"
+    },
+    "steamid": {
+      "description": "STEAM_1:y:z"
+    },
+    "steamid3": {
+      "description": "[U:1:x]"
+    },
+    "steamid64": {
+      "type": "string"
+    },
+    "vanity": {
+      "description": "custom URL name when known, otherwise null"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"steamid64 (17 digits), STEAM_1:0:x, [U:1:x], steamcommunity.com profile link or vanity name"New value: +"any SteamID format: steamid64 (17 digits), STEAM_1:0:x, STEAM_0:0:x, [U:1:x], hex, steam:hex, a 32-bit account id, a steamcommunity.com link or a vanity name"
  3. 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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavior: resolution traverses Steam and unresolvable ids return an error rather than a partial guess. It does not discuss rate limits, throttling, or latency of the network lookup, which matters for an openWorld resolver.

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

Conciseness4/5

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

Front-loaded with the 'Use when' trigger, then capability, then exclusions. Dense and mostly waste-free, though the inline enumeration of every output format partially duplicates what the output schema already conveys.

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?

Output schema exists, so return values need no explanation; the description instead covers the failure mode (error on unresolvable ids, no guessing), the input trigger, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and the id parameter's schema text already enumerates accepted formats, so the description only re-summarizes the same list. Baseline 3 applies since the schema does the heavy lifting and the description adds no syntax or normalization rules beyond it.

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?

States a specific action (resolve the steamid64 behind a vanity name or steamcommunity.com/id/ link) plus the secondary capability of returning an identity in every format. It explicitly distinguishes itself from steam_convert and steam_profile, so an agent can route without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives an explicit trigger (user supplies a vanity name or /id/ link and needs the steamid64), an explicit non-use case (pure format conversion of a known id) with a named cheaper alternative, and a second exclusion for profile data. When-to-use, when-not, and alternatives are all present.

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

All SteamGPT toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources