Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_featured_specials

Read-only

List games on sale in Steam's featured specials. Get up to 50 discounted titles with regional pricing, returned as markdown or JSON.

Instructions

List games currently ON SALE (featured specials) on the Steam store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.18.0
    • removedInput schema / $defs / FeaturedInput / properties / country_code / title
      Removed value: -"Country Code"
    • removedInput schema / $defs / FeaturedInput / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / $defs / FeaturedInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / FeaturedInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / FeaturedInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / FeaturedInput / title
      Removed value: -"FeaturedInput"
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"steam_get_featured_specialsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_featured_specialsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the 'currently ON SALE' scoping and 'featured specials' context, but does not disclose details such as regional pricing behavior or response format.

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?

A single, front-loaded sentence with no filler. Every word contributes to identifying the resource and scope.

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 simple read-only list tool, the description plus schema is adequate: readOnlyHint covers safety, and the schema documents parameters and defaults. It would be stronger if it stated the return shape (e.g., a list of games with prices/discounts), but no output schema exists.

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?

The description itself says nothing about limit, country_code, or response_format. However, the input schema's nested $defs provides descriptions and defaults for all three, so the structured data carries the parameter burden; the description adds no extra semantic value.

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 names a specific verb ('List'), a specific resource ('games currently ON SALE ... on the Steam store'), and clarifies 'featured specials' as sale items. It is clearly distinct from broader discovery tools like steam_discover, though it does not explicitly name a sibling alternative.

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?

The phrase 'currently ON SALE' implies this tool should be used when the agent needs discounted featured games, but there is no explicit when-to-use, prerequisite, or exclusion guidance relative to the many sibling store tools.

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