Skip to main content
Glama
Sign In

SteamGPT

by net.steamgpt
OverviewDiscussionsAdmin

Steam friend list

steam_friends
Read-onlyIdempotent

Use when the user asks who the friends of a Steam player are or needs the friend list for a graph check. Source: the platform snapshot of the public Steam friend graph (cache only, no live Steam call; it can be partial - absence of a friendship is not proof). detail picks token cost: short - steamid64 array, medium - steamid64 + personaname, full - raw Steam objects; use short unless names are needed. Do not use for shared friends of two players (steam_compare).

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
limitNomax friends to return, default 100
detailNoresponse detail level, default full

Output Schema

NameRequiredDescriptionDefault
countNofriends returned
friendsNoentries shaped by detail: steamid64 strings, {steamid64, personaname} or {steamid64, steam}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "friends returned",
+      "type": "integer"
+    },
+    "friends": {
+      "description": "entries shaped by detail: steamid64 strings, {steamid64, personaname} or {steamid64, steam}",
+      "type": "array"
+    }
+  },
+  "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.7/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that this is a cached snapshot with no live Steam call and that results can be partial ('absence of a friendship is not proof') – a crucial caveat an agent could not infer elsewhere. Minor tension: schema default for detail is 'full' while description advises 'use short unless names are needed', which could confuse an agent picking values.

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 trigger clause, then source caveat, then detail guidance, then exclusion – every sentence carries distinct information with no filler despite the density.

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 values needn't be explained; the description still covers the source, staleness risk, and detail-level cost, which is everything an agent needs to call it correctly.

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 coverage is 100%, so baseline is 3, and the description adds real value by explaining what each detail level returns (short=steamid64 array, medium=+personaname, full=raw objects) and the cost tradeoff, which the schema's one-line 'response detail level' does not. The limit parameter is left unmentioned.

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 verb+resource ('who the friends of a Steam player are' / friend list) and names the sibling it is not (steam_compare for shared friends). An agent can distinguish it from steam_compare and steam_profile 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?

Explicit when-to-use ('user asks who the friends... or needs the friend list for a graph check') and when-not ('Do not use for shared friends of two players (steam_compare)'), plus guidance on picking detail level by token cost.

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