Steam Scout MCP

regional_prices

Read-onlyIdempotent

Compare a Steam app's price across store regions and convert results to one currency, then sort by price to identify cheaper regional purchase options.

Instructions

Compare an app's price across store regions, converted to one currency and sorted cheapest first.

Defaults to the US, UK, Germany, France, Japan, South Korea, China, Taiwan and Hong Kong. Uses European Central Bank reference rates for conversion.

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": {
      "app_id": "<app_id>"
    },
    "name": "regional_prices"
  }
}

Input Schema

Name	Required	Default
`app_id`	Yes
`countries`	No
`convert_to`	No	USD

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior. Beyond that, the description adds genuinely useful context: results are converted to a single currency, sorted cheapest first, use ECB reference rates, and default to a specific nine-region set. It stops short of describing failure modes or how missing regions are handled.

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?

Three short sentences with no filler, and the core behavior (compare, convert, sort cheapest first) is front-loaded before the defaults. Every sentence adds information an agent could act on.

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?

There is no output schema, so the description should at least sketch the returned shape; it says results are sorted cheapest first but not what fields come back per region. Combined with the undocumented `app_id`, this is adequate but leaves real gaps for a 3-parameter tool with zero schema description coverage.

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 coverage is 0%, so the description carries full responsibility for the three parameters. It documents the `countries` default list and implies the currency-conversion parameter, but never names `convert_to`, never mentions its USD default, and leaves the required `app_id` entirely unexplained.

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 gives a specific verb and resource — comparing an app's price across store regions — plus conversion and cheapest-first sorting. It is clear what the tool returns, but it never distinguishes itself from the sibling `compare_games`, which an agent could easily confuse with a regional price comparison.

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: the description explains the default region set and conversion behavior, which hints at when to use it for cross-region pricing. It does not state when to prefer `compare_games` or `store_charts`, nor any prerequisites or exclusions.

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

Deploy Server