SteamGPT

SteamID converter

steam_convert

Read-onlyIdempotent

Use when the user wants a SteamID converted between formats - steamid64 (dec and hex), STEAM_1:0:x, legacy STEAM_0, [U:1:x], 32-bit account id, steam:hex (FiveM) or the profile URL - starting from any one of them, instantly and offline. CHEAPEST TOOL: prefer it over steam_identity whenever only format conversion is needed. Do not use for vanity names (steamcommunity.com/id/name is not a computable format - use steam_identity) or for profile data (steam_profile).

Input Schema

Name	Required	Description	Default
`id`	Yes	steamid64 (17 digits), STEAM_1:0:x, STEAM_0:0:x, [U:1:x], hex, steam:hex, a 32-bit account id or a /profiles/ link. NOT a vanity name

Output Schema

Name	Required	Description
`steamid`	No	STEAM_1:y:z
`steamid3`	No	[U:1:x]
`accountid`	No	32-bit account id
`steam_hex`	No	steam:hex form used by FiveM
`steamid64`	No
`profile_url`	No	steamcommunity.com/profiles/ link
`input_format`	No	which format the input was recognized as
`steamid64_hex`	No	steamid64 in hexadecimal
`steamid_legacy`	No	STEAM_0:y:z

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "accountid": {
+      "description": "32-bit account id"
+    },
+    "input_format": {
+      "description": "which format the input was recognized as"
+    },
+    "profile_url": {
+      "description": "steamcommunity.com/profiles/ link"
+    },
+    "steam_hex": {
+      "description": "steam:hex form used by FiveM"
+    },
+    "steamid": {
+      "description": "STEAM_1:y:z"
+    },
+    "steamid3": {
+      "description": "[U:1:x]"
+    },
+    "steamid64": {
+      "type": "string"
+    },
+    "steamid64_hex": {
+      "description": "steamid64 in hexadecimal"
+    },
+    "steamid_legacy": {
+      "description": "STEAM_0:y:z"
+    }
+  },
+  "type": "object"
+}

AddedAug 18, 2026

TDQS

A3.9/5.0

Behavior1/5

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

The annotations declare openWorldHint=true, implying interaction with an open world of external entities, while the description says the conversion is 'instantly and offline.' That is a direct contradiction. Although the description otherwise adds useful context about cheapness and format handling, the rule requires score 1 when the description contradicts 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 front-loaded with the core action, then immediately routes the agent via cheapness and exclusions. Every clause earns its place, with no filler.

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?

Given a single required input and an output schema, the description need not explain return values. It covers the accepted formats, usage preference, exclusions, and offline/instant behavior, so an agent has enough to call it correctly apart from the annotation contradiction.

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 schema already documents the single id parameter with examples and the vanity-name exclusion. The description reinforces that any supported format is accepted but does not add syntax or format details beyond the schema.

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 states a specific verb and resource: converting SteamIDs between named formats, and explicitly says it works from any one of them. It distinguishes the tool from siblings like steam_identity and steam_profile.

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?

It gives explicit when-to-use guidance ('prefer it over steam_identity whenever only format conversion is needed') and when-not-to-use guidance ('Do not use for vanity names... or for profile data'). The alternatives are named directly.

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

All SteamGPT tools Inspect

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

Need Help?