Skip to main content
Glama
Sign In

SteamGPT

by net.steamgpt
OverviewDiscussionsAdmin

Steam ban check

steam_bans
Read-onlyIdempotent

Use when the user asks whether a Steam account has a VAC, game, community or trade (economy) ban - the first check for a cheating report or before trusting a player. Returns VACBanned, NumberOfVACBans, NumberOfGameBans, DaysSinceLastBan, CommunityBanned and EconomyBan exactly as Steam reports them; DaysSinceLastBan is 0 both for banned today and never banned. Unresolvable ids or an unavailable upstream return an error result, never guessed data. Do not use for FACEIT bans (steam_faceit).

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
bansNoSteam ban object: VACBanned, NumberOfVACBans, NumberOfGameBans, DaysSinceLastBan, CommunityBanned, EconomyBan
steamid64No
provenanceNofreshness of the ban snapshot: retrieved_at, age_seconds, fresh, cache_ttl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "bans": {
+      "description": "Steam ban object: VACBanned, NumberOfVACBans, NumberOfGameBans, DaysSinceLastBan, CommunityBanned, EconomyBan"
+    },
+    "provenance": {
+      "description": "freshness of the ban snapshot: retrieved_at, age_seconds, fresh, cache_ttl"
+    },
+    "steamid64": {
+      "type": "string"
+    }
+  },
+  "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.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world traits, but the description adds genuinely non-obvious semantics: the DaysSinceLastBan=0 ambiguity (banned today vs. never banned) and the failure contract that unresolvable ids or an unavailable upstream return an error rather than guessed data. It does not mention rate limits or any auth/key prerequisites for the upstream Steam API.

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 the trigger and scope, followed by return/caveat detail and then the exclusion. Each clause carries information an agent would otherwise have to guess; nothing is 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?

For a single-parameter read tool with an output schema and full annotations, the description covers trigger, scope, exclusion, failure behavior and the one ambiguous return field. An agent has everything needed to call it correctly and interpret the result.

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 property description already enumerates every accepted SteamID format, so the schema carries the full burden. The description adds nothing about the id parameter itself, so the baseline 3 applies.

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 verb and resource ('checks whether a Steam account has a VAC, game, community or trade ban') and enumerates the ban categories it covers. It explicitly names the sibling it is not for (steam_faceit), so an agent can distinguish it from neighbors without opening any schema.

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 ('use when the user asks whether...'), two concrete scenario contexts ('first check for a cheating report or before trusting a player'), and an explicit exclusion with the alternative tool named. Nothing about when to select this vs. siblings is left to inference.

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