Skip to main content
Glama
Grinv

steam-games-mcp

by Grinv
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

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

discover_games
Read-only

Search the entire Steam catalog for games by discount, release date, Steam Deck support, and review rating. Filter sales, new releases, or Deck-verified titles in one call.

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'), Steam Deck compatibility (steam_deck), and review quality (min_review / min_reviews). Each result returns price/discount, review %, Steam Deck status 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; 'newest Deck-Verified games' → released_within_days + steam_deck. No appids needed — unlike get_items, which prices a list you already have. Note: the Steam catalog API has no release-date sort, so results are scanned popularity-first and these filters are applied over that window — great for popular titles; a niche release with very few reviews may fall outside the top count (raise count for stricter filters).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoHow many catalog entries to scan (default 50). Raise for stricter filters.
startNoPagination offset into the catalog.
countryNoCountry (cc) for prices; overrides STEAM_COUNTRY.
languageNoStore language; overrides STEAM_LANGUAGE.
min_reviewNoMinimum positive-review %, e.g. 85. Applied over the returned page.
steam_deckNoKeep only Deck-capable games: 'verified' = Deck-Verified only; 'playable' = Playable or Verified.
min_reviewsNoMinimum review count (filters out games with too few reviews).
min_discountNoMinimum discount %, e.g. 80 for '80%+ off' — this is the 'deals' filter. Omit to include full-price games.
released_afterNoKeep only games released on/after this date (YYYY-MM-DD).
released_within_daysNoAlternative to released_after: released within the last N days.

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds crucial behavioral details: no release-date sort, popularity-first scanning, that filters are applied over a window, and that niche releases may be missed. This goes beyond the 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 a single paragraph that front-loads purpose, then gives examples and a limitation note. It is efficient with only moderate verbosity; could be slightly tighter but still very readable.

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?

With 10 parameters and no output schema, the description explains return fields and the scanning limitation. It covers the key aspects needed to use the tool correctly, though more detail on pagination and ordering could help.

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. The description adds contextual examples and links parameters to user intents (e.g., min_discount for 'deals', released_within_days for 'new games'), which adds value beyond the schema descriptions.

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 various filters, and explicitly distinguishes it from get_items by noting no appids are needed. The verb 'find' and resource 'games' paired with filter capabilities make the purpose obvious.

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?

The description provides clear examples and contrasts with get_items. It advises raising count for stricter filters and warns about the popularity-first scanning. However, it does not explicitly state when not to use this tool (e.g., if you have specific appids).

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