Steam Review MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_steam_reviewC | Retrieves reviews and game information for a specific Steam application. Returns formatted review data including review scores, positive/negative counts, review texts, and basic game information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-reviews | |
| recent-reviews-analysis |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, distinct purpose focused on retrieving Steam review data.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'get_steam_review' follows a clear verb_noun pattern.
One tool is too few for a server named 'Steam Review MCP', which suggests a broader scope for interacting with Steam reviews. This minimal set severely limits functionality, such as lacking search, filtering, or update capabilities.
The tool surface is severely incomplete for a Steam review domain. It only provides retrieval for a specific application, missing essential operations like searching reviews, getting user reviews, updating data, or handling multiple games, which are typical for such a service.