Skip to main content
Glama
jhomen368

Steam Reviews MCP

by jhomen368
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_steam_games

Search Steam games by name or keywords, singly or in batch, to retrieve basic details like AppID, price, and preview image for informed purchasing decisions.

Instructions

Search for Steam games by name or keywords. Provide query for a single search or a non-empty queries array for batch searches. Returns basic game information including AppID, name, price, and preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results PER QUERY (default: 10, max: 25)
queryNoNon-blank single search query (game name or keywords)
queriesNoMultiple search queries for batch searching. May be empty when query is provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.1.1
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "properties": {
+      "queries": {
+        "minItems": 1
+      }
+    },
+    "required": [
+      "queries"
+    ]
+  }
+]
    • changedInput schema / properties / queries / description
      Previous value: -"Multiple search queries for batch searching"New value: +"Multiple search queries for batch searching. May be empty when query is provided."
    • addedInput schema / properties / queries / items / minLength
      Added value: +1
    • addedInput schema / properties / queries / items / pattern
      Added value: +"\\S"
    • removedInput schema / properties / queries / minItems
      Removed value: -1
    • changedInput schema / properties / query / description
      Previous value: -"Single search query (game name or keywords)"New value: +"Non-blank single search query (game name or keywords)"
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / query / pattern
      Added value: +"\\S"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the tool returns basic game information and supports batch searches, but does not disclose rate limits, pagination behavior, or what happens with invalid queries. The description is honest but lacks depth on edge cases and operational constraints.

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?

The description is two sentences with no fluff. It front-loads the core purpose, then explains the single vs batch usage, and ends with the return fields. Every sentence earns its place.

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 search tool with no output schema and no annotations, the description covers the main usage and return values. It lacks details on error handling, rate limits, or result ordering, but for a simple search tool, the essential information is present. The batch search constraint (max 5 queries) is in the schema, not the description, but the description mentions the non-empty array requirement.

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 the schema already documents all parameters. The description adds context by explaining the batch search option and the return fields, but it does not add significant meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the tool searches for Steam games by name or keywords and returns basic game information (AppID, name, price, preview image). It distinguishes itself from siblings like get_game_info and fetch_reviews by focusing on search and listing basic game data.

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

Usage Guidelines4/5

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

The description explains how to use the tool: provide a single query or a non-empty queries array for batch searches. It implies when to use it (searching for games) but does not explicitly state when not to use it or mention alternatives like get_game_info for detailed info. The batch search guidance is clear and useful.

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