Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_store_highlights

Read-only

Get Steam storefront lists for top sellers, new releases, coming soon, or specials. Specify section, item limit, and country for regional pricing.

Instructions

List a Steam storefront section: top sellers, new releases, or coming soon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds only the section scope and discloses nothing about output format, pagination, or regional-pricing effects, so it provides little behavioral information beyond the annotation.

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 states the action and the main variants without filler. Every word earns its place and the description is appropriately short for a simple list operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with a simple scope, the description is nearly sufficient when paired with the schema. However, it omits the 'specials' section, gives no indication of the return format, and does not steer the agent away from similar storefront-list siblings.

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

Parameters2/5

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

Schema description coverage is reported at 0%, so the description should compensate for parameter meaning. It partially covers the 'section' parameter but omits the 'specials' option, and it says nothing about 'limit', 'country_code', or 'response_format'.

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 uses a specific verb ('List') and a clear resource ('Steam storefront section'), naming three relevant section types. It is not fully precise because it omits the 'specials' section accepted by the schema and does not differentiate the tool from siblings like steam_get_featured_specials.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as steam_get_featured_specials or steam_discover. The general context is clear, but there are no exclusions or selection criteria for edge cases like specials.

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