Related Servers

Most tools have clearly distinct purposes, and the descriptions aggressively cross-reference each other ('use get_items instead', 'for X use Y'), which makes correct selection practical. However, there are tight clusters that could cause misselection: three achievement tools (get_global_achievements / get_game_achievements / get_player_achievements), two review tools, two front-page tools (get_specials / get_featured), and two game-finding tools (search_games / discover_games) — the boundaries are explained but an agent skimming could easily grab the wrong one.

All tool names are snake_case and follow a predictable get_<resource> convention for 20 of 25 tools (get_game, get_prices, get_wishlist, get_owned_games). The five exceptions (search_games, discover_games, resolve_vanity_url, find_friends_who_own, compare_players) use descriptive action verbs that match their non-trivial operations, forming a coherent secondary pattern rather than a random deviation.

25 tools puts this at the top of the 'heavy' range, but the server spans two genuinely distinct domains — store browsing/discovery (12 tools) and player/social data (13 tools) — so each tool plausibly earns its place. It is slightly over the ideal size and could benefit from consolidation (e.g., get_specials folded into get_featured, get_prices into get_items), but the two-domain structure keeps it navigable.

For a read-only Steam data server, the surface is remarkably complete: store search, details, pricing, reviews, trends, news, achievements, discovery, and player-side coverage including wishlists, friends, owned games, shared libraries, bans, and recommendations. There are no dead ends — search_games feeds appids and resolve_vanity_url feeds SteamIDs. Minor gaps exist: no market/workshop data, no bulk profile summary lookups, and discover_games' popularity-first scan is a documented practical limitation.