Steam Scout MCP

search_games

Read-onlyIdempotent

Search the Steam store by game name to retrieve app IDs, regional prices, and supported platforms for a specified country and result limit.

Instructions

Search the Steam store by name. Returns app_id, price in the region's currency, platforms.

country: two-letter store region (US, GB, DE, JP, KR, CN...). limit: 1-25.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_games"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`query`	Yes
`country`	No	US

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly/openWorld/idempotent, so safety is covered. The description adds value by listing returned fields (app_id, price, platforms), which matters since there is no output schema, but says nothing about match fuzziness, empty-result behavior, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded verb+resource+returns in one sentence, then a compact parameter note. Nothing is wasted, though the parameter block is written as an unlabeled fragment rather than a clean list.

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?

Adequate for a 3-param read tool: purpose, region semantics, and return fields are all present. Gaps remain on result ordering, behavior when the query matches nothing, and how the caller should follow up (e.g. game_details for the returned app_id).

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

Parameters4/5

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

With 0% schema coverage the description must carry the load, and it does for two of three params: country is defined as a two-letter store region with five concrete examples, and limit is bounded to 1-25. 'query' is left to be inferred from 'by name' rather than being explicitly described as the search string.

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?

States a specific verb+resource ('Search the Steam store by name') and immediately names the return fields, so an agent can tell it apart from game_details (single lookup) or store_charts (browse). It stops short of explicitly contrasting with the closest sibling, compare_games.

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?

Usage is only implied by 'by name' — an agent infers this is the entry point when it has a title string but no app_id. There is no explicit when-to-use statement, no exclusion, and no routing to game_details for follow-up detail lookups.

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

Deploy Server