Skip to main content
Glama
Sign In

SteamGPT

by net.steamgpt
OverviewDiscussionsAdmin

Compare two players

steam_compare
Read-onlyIdempotent

Use when the user asks to compare two Steam players, whether two accounts are related or share friends, or for smurf and alt-account hints: 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. Do not use for a single player (steam_summary) or for more than two players (steam_batch).

Input Schema

NameRequiredDescriptionDefault
id1Yesany 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
id2Yesany 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
aNosummary of the first player: identity, account, Steam bans, FACEIT
bNosummary of the second player
shared_friendsNofriends present in both snapshots; an empty list is not proof the players are unrelated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "a": {
+      "description": "summary of the first player: identity, account, Steam bans, FACEIT"
+    },
+    "b": {
+      "description": "summary of the second player"
+    },
+    "shared_friends": {
+      "description": "friends present in both snapshots; an empty list is not proof the players are unrelated"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • 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"
  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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond them: it warns this is the HEAVIEST tool because it builds two summaries plus both friend graphs, which tells the agent about cost/latency and why to avoid calling it casually. No auth or rate-limit detail, and the friend-graph scan over 'full friend lists' could hint at scale limits, but the cost disclosure is the key one.

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?

Two sentences, front-loaded with the 'Use when' trigger, then the cost warning, then the negative routing. Every clause earns its place and no format details are duplicated from the schema.

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?

An output schema exists, so return structure needn't be explained. Given the tool's cost and complexity, the description covers triggers, exclusions, alternatives and the expensive side effects (two summaries plus both friend graphs) — everything an agent needs to decide and invoke 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?

Schema description coverage is 100% and both id1/id2 document every accepted SteamID format in detail, so the description does not need to repeat it. The description adds no parameter-level meaning beyond what the schema states; baseline 3 applies since the schema carries the 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?

Specific verb ('compare') plus resource ('two Steam players') plus an enumeration of what is compared: identity, account age, visibility, bans, FACEIT, shared friends. It explicitly distinguishes itself from steam_summary (one player) and steam_batch (more than two), so an agent can route 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?

The first sentence gives concrete trigger scenarios (compare two players, are accounts related, share friends, smurf/alt hints) and the last sentence names both exclusions and the sibling to use instead. Nothing 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