Skip to main content
Glama

Discover games (deals, new releases, Steam Deck, rating)

discover_games
Read-only

Find games from the Steam catalog filtered by discount, release date, platform, review quality, user tags, and hardware compatibility including Steam Deck, SteamOS, Steam Machine, and Steam Frame.

Instructions

Find games across the whole Steam catalog (keyless), filtered by ANY combination of: discount (min_discount — for 'what's on sale'), release recency (released_after / released_within_days — for 'new games'), hardware compatibility (steam_deck for Steam Deck, steam_os for SteamOS in general, steam_machine for the Steam Machine console specifically, steam_frame for the Steam Frame VR headset), native OS build (platform — windows/mac/linux), review quality (min_review / min_reviews), and user tags (tags — e.g. ['Roguelike', 'Deckbuilding'] for 'games like X'). Each result returns price/discount, review %, all four compat statuses, a vr_support flag (none/supported/required), popular tags, a clickable store_url, discount_end (when a deal expires) and release date in one call. Examples: '>80% off with 90%+ reviews' → set min_discount + min_review; 'recent well-reviewed games that run on Steam Deck' → set released_within_days + steam_deck + min_review; 'roguelike deckbuilders on sale' → tags:['Roguelike','Deckbuilding'] + min_discount; 'games that run on the Steam Machine' → steam_machine; 'games that run on SteamOS' → steam_os. No appids needed — unlike get_items, which prices a list you already have. For 'games like X' from a SINGLE named title, get its tags via get_items and pass them here; for taste inferred from the player's WHOLE library instead, use get_recommended_games (key-gated). Note: min_discount is filtered server-side, and setting released_after/released_within_days also excludes not-yet-released games server-side — but the actual date cutoff, plus compat, platform, review and tag filtering, have no server-side support in the Steam catalog API, so those are scanned popularity-first and applied afterward over that same window — great for popular titles; a niche match may fall outside the top count (raise count for stricter filters).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoKeep only games carrying ALL of these user tags (case-insensitive), e.g. ['Roguelike','Deckbuilding']. Use exact Steam tag names — a misspelled/unrecognized one isn't an error, it just matches nothing. Applied over the scanned popularity window, so raise `count` when combining niche tags.
countNoHow many catalog entries to scan (1-200). Default 50. Raise for stricter filters.
startNoPagination offset into the catalog (default 0).
countryNoCountry (cc) for prices/currency; overrides STEAM_COUNTRY for this call.
languageNoStore language (e.g. english, russian); overrides STEAM_LANGUAGE for this call.
platformNoNATIVE-build filter: keep only games shipping a native build for this OS (windows/mac/linux). 'linux' = a native Linux/SteamOS port. This is NOT Proton — for games that run via Proton compatibility use steam_os / steam_deck instead. Each result's `platforms` field lists its native builds, while steam_os/steam_deck report Proton compatibility, so native vs Proton stay distinct.
steam_osNoSteamOS compatibility — how well it runs on SteamOS in general (via Proton): 'verified' = SteamOS-Verified only; 'playable' = Playable or Verified. For a NATIVE Linux build instead, use platform:'linux'; for the Steam Machine console specifically, use steam_machine.
min_reviewNoMinimum positive-review %, e.g. 85. Applied over the returned page.
steam_deckNoSteam Deck compatibility (runs via Proton): 'verified' = Deck-Verified only; 'playable' = Playable or Verified. Not a native Linux build — see `platform` for that.
min_reviewsNoMinimum review count (filters out games with too few reviews).
steam_frameNoSteam Frame (VR headset) compatibility: 'verified' = Frame-Verified only; 'playable' = Playable or Verified.
min_discountNoMinimum discount %, e.g. 80 for '80%+ off' — this is the 'deals' filter. Omit to include full-price games.
steam_machineNoSteam Machine (Valve's console) compatibility (via Proton): 'verified' = Steam-Machine-Verified only; 'playable' = Playable or Verified. Its own rating, distinct from the general steam_os one.
released_afterNoKeep only games released on/after this date (YYYY-MM-DD).
released_within_daysNoAlternative to released_after: released within the last N days.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dealsYes
returnedYesHow many results survived every filter, out of the scanned window (see `count`).
total_matchingYesCount from whichever filters Steam actually applies server-side — min_discount, and (if released_after/released_within_days was set) excluding not-yet-released games — or the whole catalog's size if neither was given. NOT the number of games matching tags/platform/compat/review/the exact release-date cutoff, which have no server-side filter and this tool applies only over the scanned `count`-sized window below. Don't read this as 'N games match all my filters' — use `returned` for that instead.
Behavior5/5

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

The description discloses that most filters are applied client-side over a popularity window, affecting niche matches, and notes server-side vs client-side filtering limitations, adding value beyond readOnlyHint and openWorldHint annotations.

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 somewhat lengthy but well-structured with clear sections, examples, and notes. It could be slightly more concise, but the detail serves a complex tool.

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?

Given the tool's complexity (15 parameters, 0 required, output schema exists), the description covers all aspects: parameter meanings, filtering behavior, return fields, and limitations, making it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description enriches parameter understanding by explaining nuances like platform vs Proton compatibility, tag filtering, and the interaction between count and filter strictness.

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 the tool finds games across the Steam catalog with many filters, and distinguishes from siblings like get_items and get_recommended_games.

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?

It provides explicit when-to-use guidance, contrasting with get_items (for pricing a known list) and get_recommended_games (for taste from whole library), and includes examples for common scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/steam-games-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server