Skip to main content
Glama
Sign In
Steam Scout MCP

Steam Scout MCP

by cyanspearfitting4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

review_summary

Read-onlyIdempotent

Retrieve Steam game review sentiment and sample recent reviews by app ID, including score, positive percentage, and totals; optionally filter by language.

Instructions

Steam review score (e.g. "Very Positive"), positive percentage, totals and a few recent reviews.

language: "all" or a Steam language name such as english, japanese, koreana, schinese.

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

Input Schema

NameRequiredDescriptionDefault
app_idYes
languageNoall
recent_samplesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that the payload is a summary plus only 'a few recent reviews', which sets expectations about data volume. It says nothing about rate limits, caching, or behavior when a game has no reviews, which would be the value-add a 4 or 5 requires.

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?

The returned-content summary is front-loaded in a single efficient sentence with no filler. The trailing 'language:' fragment is tersely structured and reads slightly like a dangling note rather than prose, but it is short and earns its place by documenting otherwise undocumented enum-like values.

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?

With no output schema, the description correctly takes on the burden of describing return values and does so adequately. But with three parameters and no per-parameter schema documentation, leaving app_id and recent_samples unexplained leaves an agent guessing about input semantics.

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 0%, so the description must compensate. It does so well for language, spelling out 'all' plus concrete Steam language names (english, japanese, koreana, schinese) that the schema lacks. However, app_id is never explained, and recent_samples is only obliquely implied by 'a few recent reviews' rather than tied to the parameter.

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 (Steam reviews) and enumerates what comes back: score label, positive percentage, totals, and recent samples. That is far more informative than a bare name. It does not explicitly differentiate from siblings like game_details, which could plausibly also surface review text, so it stops short of a 5.

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 statement of when to call this instead of search_games, game_details, or compare_games, and no prerequisites such as needing a Steam app_id. The only guidance present is a hint about the language parameter's accepted values, which is parameter semantics rather than usage routing.

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