SteamGPT

Compare two players

steam_compare

Read-onlyIdempotent

Two players side by side: identity, account age, visibility, Steam bans, FACEIT and shared friends (compared over the full friend lists). HEAVIEST tool - it builds two summaries plus both friend graphs; for a single player prefer steam_summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id1`	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
`id2`	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

Schema Changelog

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

Changed2 schema fields changedAug 18, 2026

changedInput schema / properties / id1 / 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"

changedInput schema / properties / id2 / 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.8/5.0

Behavior5/5

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

The description warns that this tool is the 'HEAVIEST' and explains why: it builds two summaries plus both friend graphs. This adds significant behavioral context beyond the annotations (readOnlyHint etc.), informing the agent of high computational cost and data load.

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 two sentences: the first clearly explains what the tool does, the second provides critical usage guidance. Every sentence is essential and front-loaded. No verbosity.

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 has no output schema, the description explains what data will be returned (identity, account age, etc.) but does not detail the structure of the friend graph or shared friends output. It is complete enough for a high-level compare tool, but could specify output format minimally.

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 description coverage is 100%, so the schema already documents the two parameters well. The description adds no additional parameter details beyond the schema, but the schema itself is thorough. Score 4 reflects that the description does not detract and the schema is complete.

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 specifies the verb 'compare' and the resource 'two players', and lists the exact data fields (identity, account age, visibility, Steam bans, FACEIT, shared friends). It also distinguishes this tool from siblings by noting the comparison of full friend lists and the building of friend graphs.

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?

The description explicitly states this is the 'HEAVIEST tool' and advises using 'steam_summary' for a single player instead. This provides clear when-to-use and when-not-to-use guidance, with a named alternative.

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

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

Need Help?