Skip to main content
Glama

SteamGPT

by net.steamgpt

Steam profile

steam_profile
Read-onlyIdempotent

Steam summary only (raw GetPlayerSummaries object + 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.

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

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false), the description adds critical behavioral details: caching policy (48 hours), lazy fetching for unknown profiles, private profile handling (public subset, not error), and unresolvable ID behavior (error). This fully informs the agent of the tool's behavior.

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 concise at three sentences, each serving a distinct purpose: purpose, usage context, and edge cases. It is front-loaded with the core purpose and wastes no words.

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 (one parameter, no output schema), the description covers purpose, caching, private profile behavior, and error handling. It does not detail the return structure beyond 'raw GetPlayerSummaries object', but that is a known Steam API object. Minor gap: no mention of rate limits or authentication, but annotations imply open access. Overall adequate.

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 already provides 100% coverage with a detailed description of the 'id' parameter. The tool description does not add new semantic meaning about the parameter beyond what the schema specifies. Baseline 3 is appropriate as the schema carries the burden.

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 clearly states the tool returns a 'raw GetPlayerSummaries object + SteamID conversions' and identifies it as a 'cheapest profile tool', distinguishing it from siblings like steam_summary and steam_convert. It specifies the verb (summary only) and resource (profile), making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides context for when to use this tool: 'cheapest profile tool' and mentions data freshness ('no older than 48 hours, unknown profiles fetched live'). It does not explicitly exclude alternatives or state when not to use it, but the guidance is clear enough for an agent to infer its lightweight, cached nature.

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