Skip to main content
Glama

Markan: Steam market data

Get Steam game data

get_games
Read-only

Data for up to 50 Steam games by Steam ID. Prices are USD cents (basePrice, minimumPrice; minimumPrice is the lowest price Markan has seen, null if not yet known). Choose fields to keep the answer small; default: steamId, title, type, releaseDate, basePrice, numReviews, reviewScoreDesc, shortDescription, tags, genres, developers, publishers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "steam_ids": "<steam_ids>"
    },
    "name": "get_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoWhich fields to return; leave out for a useful default set (title, release date, price, reviews, short description, tags...). Prices are in US cents.
steam_idsYesSteam app IDs (the number in a store URL), from find_games or search_games.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"Which fields to return; leave out for a useful default set (title, release date, price, reviews, short description, tags...). Prices are in US cents."
    • addedInput schema / properties / steam_ids / description
      Added value: +"Steam app IDs (the number in a store URL), from find_games or search_games."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond that: price units in USD cents, the meaning of minimumPrice ('lowest price Markan has seen, null if not yet known'), and the 50-game cap — details not carried by the annotations or schema.

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?

Three tight sentences: scope first, then pricing semantics, then field-selection advice with defaults. Nothing is filler, though the field enumeration runs long relative to the rest and partly duplicates the schema's enum.

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?

Without an output schema, the description carries the burden of describing returns, and the default field list plus price semantics do that adequately for a read-only bulk lookup. Only edge behaviors (invalid or unknown IDs, partial results) are left unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, including the maxItems of 50 and the enum of fields. The description restates the default field set and price units, adding marginal but not substantial meaning; baseline 3 applies when the schema does the heavy lifting.

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?

States a specific resource and scope: 'Data for up to 50 Steam games by Steam ID', which is clearly a bulk-fetch by known IDs rather than a search. It does not explicitly distinguish itself from find_games/search_games, though the schema's reference to those for obtaining IDs implies the split.

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?

Offers concrete guidance on field selection ('Choose fields to keep the answer small') and lists the default field set, which helps an agent decide how to call it. It gives no explicit when-to-use versus siblings — the reader must infer that this tool is for fetching details once IDs are already known.

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