Skip to main content
Glama

Steam

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses important behavioral requirements: requires OAuth account, phone verification, 10/day SMS cap, and the always-on feed. The idempotentHint is slightly ambiguous against 'new subscription id' but the description doesn't explicitly conflict; it adds value beyond the annotations by explaining verification and rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured: it leads with the main action, then return value, auth requirement, supported types, and delivery options. Each sentence contributes useful information, though the delivery details are also duplicated in the schema, making it slightly redundant.

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's complexity (5 subscription types, nested delivery object) and no output schema, the description covers the essential aspects: purpose, return value, auth, type-specific params, and delivery options. It doesn't explain how to manage subscriptions or what the output format looks like beyond the id, but sibling tools like list_subscriptions and unsubscribe cover those aspects.

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?

The schema already provides 100% parameter descriptions with examples for all subscription types. The description reinforces this with examples like items:['5.02'] and delivery constraints (phone must be verified, 10/day cap), adding practical meaning beyond the schema's baseline.

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 clearly states a specific action ('Create a proactive monitoring subscription') targeting a defined resource ('live-data event stream'). It distinguishes from sibling tools like list_subscriptions, unsubscribe, and recent_alerts by focusing on creation, not listing or removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when to use: describes supported subscription types and delivery channels. It also references how to consume the feed (via recent_alerts or the public registry endpoint), giving practical guidance. However, it doesn't explicitly name alternative tools for other operations, but the sibling list implies them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Steam toolsInspect
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

C2.9/5.0
Disambiguation2/5

Many tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, while deep_research, discover_tools, and suggest_questions all serve meta/onboarding purposes. The Steam-specific tools are distinct, but they are drowned out by a large unrelated set (Polymarket, Pipeworx, npm scanning) that makes selection confusing.

Naming Consistency2/5

Tool names follow no single convention: some are verb_noun (resolve_vanity_url, generate_llms_txt), some are noun-only (app_details, player_stats), and others use domain prefixes inconsistently (polymarket_arbitrage, ask_pipeworx_grounded, deep_research). The mix of descriptive and vague names (process, run, execute) adds to the inconsistency.

Tool Count2/5

At 45 tools, the server is heavily overloaded, especially for a server named 'Steam' where only about a third of the tools actually relate to Steam. The rest belong to Pipeworx, Polymarket, and other unrelated domains, making the scope unclear and the tool count far too large for a focused purpose.

Completeness3/5

For the Steam domain, the server covers a reasonable range: app details/news, player counts, friends, owned games, achievements, stats, bans, levels, and summaries. However, notable gaps exist such as store search, reviews, wishlist, or any user inventory/trading features. The non-Steam tools add breadth but do not address these missing Steam operations.

Resources