SteamGPT

Steam profile

steam_profile

Read-onlyIdempotent

Use when the user asks about one Steam account itself - nickname, avatar, profile visibility, creation date, online status, current game - and nothing else. Returns the raw GetPlayerSummaries object plus SteamID conversions; cheapest profile tool, data no older than 48 hours, unknown profiles are fetched live from Steam. Private profiles return the public subset of fields (not an error); unresolvable ids return an error result. Do not use for bans, FACEIT or friends (steam_summary or the narrow tools).

Input Schema

Name	Required	Description	Default
`id`	Yes	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

Output Schema

Name	Required	Description
`ids`	No	the same account in every SteamID format
`steam`	No	raw Steam GetPlayerSummaries object
`canonical`	No	steamid64 and canonical URL of this player
`steamid64`	No
`provenance`	No	per source: retrieved_at, age_seconds, fresh, cache_ttl

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "canonical": {
+      "description": "steamid64 and canonical URL of this player"
+    },
+    "ids": {
+      "description": "the same account in every SteamID format"
+    },
+    "provenance": {
+      "description": "per source: retrieved_at, age_seconds, fresh, cache_ttl"
+    },
+    "steam": {
+      "description": "raw Steam GetPlayerSummaries object"
+    },
+    "steamid64": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 18, 2026

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"

First observedAug 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses freshness (no older than 48 hours), live fallback behavior for unknown profiles, private-profile behavior (public subset returned, not an error), unresolvable-id behavior (error result), and that the response includes raw GetPlayerSummaries data plus SteamID conversions. It also flags this as the cheapest profile tool.

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?

Three sentences, front-loaded with usage and scope. Each sentence adds distinct information: selection criteria, return/behavioral details, and exclusions. No filler or repetition.

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?

With annotations covering safety, a fully documented single parameter, and an output schema, the description fills the remaining gaps: freshness, private-profile handling, live fetching, and failure behavior. Nothing an agent needs in order to select or invoke it correctly is missing.

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?

Schema coverage is 100% and already documents all accepted SteamID formats, so the schema carries most of the burden. The description still adds relevant parameter behavior by noting SteamID conversion in the response and error handling for unresolvable ids, which goes slightly 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 names the exact resource (one Steam account) and enumerates the fields returned: nickname, avatar, profile visibility, creation date, online status, current game. It explicitly separates this from bans, FACEIT, and friends, so the agent can distinguish it from every sibling.

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 criteria ('when the user asks about one Steam account itself ... and nothing else') and explicit when-not-to-use guidance ('Do not use for bans, FACEIT or friends'), naming steam_summary and the narrower tools as alternatives.

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?