Skip to main content
Glama
Sign In

SteamGPT

by net.steamgpt
OverviewDiscussionsAdmin

FACEIT profile

steam_faceit
Read-onlyIdempotent

Use when the user asks how good a CS2 player is on FACEIT - level, ELO, country, nickname - or whether a FACEIT account is banned. Returns the FACEIT player object plus known FACEIT bans; players without a FACEIT account return a result saying so - absence is reported explicitly, never silently. Do not use for Steam (VAC/game) bans (steam_bans) or for match history and per-match stats, which SteamGPT does not have.

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
bansNoknown FACEIT bans
noteNopresent only when no FACEIT profile is known
faceitNoFACEIT player object (nickname, country, games.cs2.skill_level, games.cs2.faceit_elo) or null when no FACEIT profile is known
steamid64No
provenanceNofreshness of the FACEIT snapshot

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": "known FACEIT bans",
+      "type": "array"
+    },
+    "faceit": {
+      "description": "FACEIT player object (nickname, country, games.cs2.skill_level, games.cs2.faceit_elo) or null when no FACEIT profile is known"
+    },
+    "note": {
+      "description": "present only when no FACEIT profile is known"
+    },
+    "provenance": {
+      "description": "freshness of the FACEIT snapshot"
+    },
+    "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.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile needs no repeating. The description adds genuinely useful behavior beyond that: it returns the player object plus known FACEIT bans, and explicitly reports absence rather than returning empty. However, with an output schema present, the return-shape detail is modest incremental value, placing it just above baseline.

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?

Front-loaded with the trigger condition, then return behavior, then exclusions — a natural decision order. Roughly three sentences, every one carrying routing or behavioral weight, with no restated title or 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 full annotations and an output schema, this covers everything an agent needs: the trigger, the returned data, the no-account edge case, and the sibling it should not be confused with. Nothing material 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 single `id` property already enumerates every accepted SteamID format, so the description adds no parameter meaning. Baseline 3 applies when the schema carries the full load.

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 resource (FACEIT CS2 profile) and the exact data returned: level, ELO, country, nickname, plus ban status. It also contrasts itself with the sibling steam_bans, so an agent can distinguish it from VAC/game-ban lookups without opening a 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?

Opens with an explicit trigger ('Use when the user asks how good a CS2 player is on FACEIT...') and then states exclusions: not for Steam bans (routing to steam_bans) and not for match history, which the server doesn't have. Both the when and the when-not are named, along with the alternative sibling.

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