Skip to main content
Glama

SteamGPT

by net.steamgpt

FACEIT profile

steam_faceit
Read-onlyIdempotent

FACEIT player object (nickname, country, per-game skill level and ELO) plus known FACEIT bans. Players without a FACEIT account return an error result saying so - absence of FACEIT data is reported explicitly, never silently.

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds valuable behavioral context: it explicitly states that absence of FACEIT data results in an error message, not silent omission. This is beyond the annotations and helps the agent understand error handling.

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?

The description is concise (two sentences) and front-loaded with the key purpose. The first sentence is slightly dense with parentheses, but it remains efficient and avoids unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 parameter, no output schema, rich annotations), the description covers the essential behavior: what data is returned, error handling, and the explicit nature of missing accounts. It is complete enough for an agent to use correctly.

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?

The input schema has 100% description coverage, fully detailing the 'id' parameter with multiple SteamID formats. The description adds no additional parameter-specific meaning beyond what the schema provides. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a FACEIT player object with specific fields (nickname, country, per-game skill level, ELO) plus bans. It also clarifies behavior when no account exists. However, it does not explicitly differentiate from sibling tools like steam_profile or steam_bans, which could also return player or ban data.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs. alternatives such as steam_bans, steam_profile, or steam_identity. The description only mentions error handling for missing accounts, which is helpful but does not help the agent decide between tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Tools are mostly distinct: steam_identity for ID resolution, steam_bans for bans, steam_faceit for FACEIT, steam_friends for friends, steam_batch for bulk, steam_compare for comparison. Minor overlap exists between steam_profile and steam_summary, but descriptions clarify steam_profile is the raw/cheapest summary while steam_summary is a richer overview with includes.

Naming Consistency5/5

All tool names follow a consistent steam_<noun> pattern in lowercase snake_case. The prefix clearly groups them under the Steam domain, and each noun reflects the specific data type or operation, making the naming predictable and readable.

Tool Count5/5

With 8 tools, the server is well-scoped for a Steam data API. Each tool covers a distinct aspect (identity, bans, profile, friends, FACEIT, batch, compare), and none feel redundant or unnecessary. The count is within the ideal 3-15 range.

Completeness4/5

The toolset covers core player data needs: identity resolution, profile summaries, bans, friends, FACEIT, batch lookups, and comparison. Minor gaps exist (e.g., no direct game/playtime data), but for the apparent purpose of player review and cheating reports, the coverage is solid.

Resources