Skip to main content
Glama
Grinv

Steam MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get current discounts

get_specials
Read-only

Retrieve current Steam store front page specials with discount percentages and original/final prices. No API key required.

Instructions

List games currently on special (discounted) on the Steam store front page, with the discount % and original/final price. For ALL catalog discounts (not just the front page), use discover_games with min_discount. No API key required.

Input Schema

NameRequiredDescriptionDefault
countryNoCountry (cc) for prices/currency and regional availability; overrides STEAM_COUNTRY for this call. Must be a real Steam store region — the two-letter shape is all that's checked here, and Steam answers an unrecognized code with US prices rather than an error, so a typo returns plausible numbers for the wrong country.
languageNoStore language for the text fields. Use Steam's own language NAME — english, russian, schinese/tchinese — not an ISO code like en/ru/zh. An unrecognized value is never an error: text comes back in English and any `tags` list comes back EMPTY, which reads as 'this game has no tags' rather than as a bad language. (Filtering BY tags is the one loud case — it fails outright.) Overrides STEAM_LANGUAGE for this call. This is the content language only — prices and regional availability follow `country`.

Output Schema

NameRequiredDescriptionDefault
specialsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.14.0
    • changedInput schema / properties / country / description
      Previous value: -"Country (cc) for prices/currency; overrides STEAM_COUNTRY for this call."New value: +"Country (cc) for prices/currency and regional availability; overrides STEAM_COUNTRY for this call. Must be a real Steam store region — the two-letter shape is all that's checked here, and Steam answers an unrecognized code with US prices rather than an error, so a typo returns plausible numbers for the wrong country."
    • changedInput schema / properties / language / description
      Previous value: -"Store language (e.g. english, russian); overrides STEAM_LANGUAGE for this call."New value: +"Store language for the text fields. Use Steam's own language NAME — english, russian, schinese/tchinese — not an ISO code like en/ru/zh. An unrecognized value is never an error: text comes back in English and any `tags` list comes back EMPTY, which reads as 'this game has no tags' rather than as a bad language. (Filtering BY tags is the one loud case — it fails outright.) Overrides STEAM_LANGUAGE for this call. This is the content language only — prices and regional availability follow `country`."
    • removedOutput schema / properties / specials / items / properties / final_price / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / specials / items / properties / final_price / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / specials / items / properties / original_price / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / specials / items / properties / original_price / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / specials / items / properties / store_url / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / specials / items / properties / store_url / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changedv0.13.1
    • addedOutput schema / properties / specials / items / properties / final_price / description
      Added value: +"Current price, or null when this section's payload carries no price — which is every `coming_soon` entry (not yet priced, NOT free) and any free-to-play title. Call get_game or get_items on the appid when you need to tell those two apart."
  3. Changed1 schema field changedv0.12.1
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv0.10.5
  5. Removedv0.10.4
  6. Addedv0.10.4
  7. Removedv0.9.0
  8. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, covering safety. The description adds the scope constraint (front page only) and the no-key requirement, but does not disclose any other behavioral traits (e.g., pagination, limits, edge cases). With annotations carrying the main safety profile, this is adequate but not rich.

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?

Two sentences with zero waste. The core purpose and output are front-loaded, followed by the alternative and a key requirement. Every sentence earns its place.

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?

The tool is simple, has an output schema (so return values need no description), and the schema fully documents parameters. The description covers scope and the alternative. With readOnly annotations covering safety, nothing an agent needs to call it correctly is missing.

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% and both parameters have detailed descriptions including edge-case behavior (unrecognized country returns US prices, unrecognized language returns empty tags). The description adds nothing about parameters, so baseline 3 applies.

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 states a specific verb and resource ('List games currently on special (discounted) on the Steam store front page') and details the output (discount % and original/final price). It explicitly differentiates from a sibling by directing to discover_games for all-catalog discounts, making it unambiguous.

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 clearly states when to use this tool (front-page specials) and when not (all catalog discounts → discover_games with min_discount). It also notes 'No API key required,' a practical usage hint. This is explicit routing to the correct alternative.

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

Deploy Server

Other Tools