Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Steam Web API: profiles, owned games, achievements, app news, player counts.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
47.4% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-steam
GitHub Stars
0
Server Listing
mcp-steam

TDQS

B3/5.0

Scored across 45 tools

Disambiguation2/5

The set conflates two entirely unrelated products — 14 Steam Web API tools plus ~31 Pipeworx data-platform/meta tools — under the name 'Steam', so an agent cannot infer the server's scope. Even within families there is heavy overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all route the same underlying data, and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread have fuzzy boundaries. player_summary vs player_summaries (single vs batch) is the one Steam pair that invites misselection.

Naming Consistency4/5

Nearly all tools are snake_case, which is consistent and readable. Verb_noun (compare_entities, resolve_entity, discover_tools) is mixed with bare noun phrases (app_details, app_news, entity_profile), and player_summary/player_summaries differ only by plural, but the overall convention holds.

Tool Count2/5

45 tools is heavy for what is nominally a Steam server, and the count reflects two merged products rather than one coherent scope. The 14 Steam tools alone would be well-scoped; the added ~31 Pipeworx tools make the set bloated and mismatched with the stated identity.

Completeness3/5

The Steam portion is fairly complete read coverage (app details/news, player profiles, owned games, recently played, achievements, stats, bans, level, friends, player count, vanity URL), though it lacks write/review operations. The Pipeworx portion is vast and cross-cutting, so coverage is hard to assess as a single domain.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources