Skip to main content
Glama

Markan: Steam market data

Find Steam games by tags, price and release date

find_games
Read-only

Find Steam games matching filters, e.g. every game tagged both 'Cozy' and 'Farming Sim', released since 2022, priced $10-25, with at least 100 reviews. Tags are Steam's user tags (case-insensitive); all given tags must match. Returns up to 50 games, sorted by review count unless asked otherwise, plus how many matched in total. Use estimate_sales on the results for sales estimates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoMost reviews first, newest or oldest release first, or cheapest first.reviews
tagsNoSteam tags, e.g. ["Cozy", "Farming Sim"].
typeNoGames, DLC, or both.game
limitNoHow many games to return.
max_reviewsNoMost Steam user reviews, e.g. to leave out breakout hits.
min_reviewsNoFewest Steam user reviews. Reviews track sales, so this filters out games that sold little.
max_price_usdNoHighest list price (before discounts) in US dollars.
min_price_usdNoLowest list price (before discounts) in US dollars, e.g. 9.99. 0 includes free games.
released_afterNoYYYY-MM-DD (inclusive).
released_beforeNoYYYY-MM-DD (inclusive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many games to return."
    • addedInput schema / properties / max_price_usd / description
      Added value: +"Highest list price (before discounts) in US dollars."
    • addedInput schema / properties / max_reviews / description
      Added value: +"Most Steam user reviews, e.g. to leave out breakout hits."
    • addedInput schema / properties / min_price_usd / description
      Added value: +"Lowest list price (before discounts) in US dollars, e.g. 9.99. 0 includes free games."
    • addedInput schema / properties / min_reviews / description
      Added value: +"Fewest Steam user reviews. Reviews track sales, so this filters out games that sold little."
    • addedInput schema / properties / sort / description
      Added value: +"Most reviews first, newest or oldest release first, or cheapest first."
    • addedInput schema / properties / type / description
      Added value: +"Games, DLC, or both."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-open-world operation. Beyond that, the description discloses important behavior: tags are case-insensitive and conjunctive, results are capped at 50, default sort is by review count, and a total match count is returned.

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

Conciseness5/5

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

The description is a compact, front-loaded paragraph. The example query and operational notes each contribute useful information without redundant restatement of the schema.

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?

For a 10-parameter, read-only search tool with no output schema, the description covers the essential return behavior: up to 50 results, default sorting, and total match count. It is nearly complete, though it could briefly clarify that results are not paginated beyond the limit or how empty matches are represented.

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 the baseline is 3. The description still adds value by clarifying that all supplied tags must match and by framing review thresholds in terms of sales and breakout-hit exclusion, which complements the schema's individual parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Find Steam games') and summarizes supported filters with a concrete example. It does not explicitly distinguish itself from sibling tools like search_games or get_games, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

It provides a useful example query and points to estimate_sales for follow-up sales estimates. However, it gives no explicit guidance on when to use this tool versus search_games or get_games, leaving the primary alternative-selection question implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources