Skip to main content
Glama
Sign In
Steam Scout MCP

Steam Scout MCP

by cyanspearfitting4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

game_details

Read-onlyIdempotent

Fetch a Steam app's store page facts—description, developers, release date, price, genres, and languages—by app ID to answer game research questions.

Instructions

Store page facts for one app: description, developers, release date, price, genres, languages.

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": "game_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
countryNoUS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds value by inventorying the fields returned, but says nothing about how the country parameter affects results or whether the response is a single object.

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?

One compact sentence that front-loads the scope ('for one app') before the field list. Nothing is wasted, though it is a fragment rather than a fully structured statement of intent.

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 two-parameter read-only tool with no output schema, the field enumeration is useful compensation, but the meaning of country and its effect on price/language data is missing — a notable gap given the regional_prices sibling.

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 0%, so the description must compensate, yet it never mentions the country parameter (which defaults to 'US') or what app_id refers to. Listing the returned fields is not the same as explaining the inputs, and the regional sensitivity implied by the country default is left entirely unstated.

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 names the resource precisely (store page facts for a single app) and enumerates the facts returned — description, developers, release date, price, genres, languages. That is enough to distinguish it from search_games or review_summary, but it never explicitly differentiates itself from siblings like player_count, which also operate on one app.

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?

There is no guidance on when to call this tool versus alternatives such as regional_prices or search_games, and no prerequisites are stated. The agent must infer usage purely from the phrase 'one app'.

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