Skip to main content
Glama
Sign In
Steam Scout MCP

Steam Scout MCP

by cyanspearfitting4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

store_charts

Read-onlyIdempotent

Fetch current Steam store charts by region to identify top sellers, new releases, specials, or coming soon titles, with adjustable result limits.

Instructions

Current Steam store charts for a region: top sellers, new releases, specials or coming soon.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "store_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartNotop_sellers
limitNo
countryNoUS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the description only needs to add context. It adds that results are 'current' and region-scoped, but says nothing about return format, pagination, or behavior for an invalid country/region code.

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?

A single front-loaded sentence with zero filler; the resource and its variants come first and nothing is repeated unnecessarily.

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 simple read tool whose annotations carry the safety profile, the description covers the essential 'what you get' dimension. However, with no output schema, an agent still doesn't know what a chart entry contains or how 'limit' and 'country' behave, which is a real gap given 0% schema 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 description coverage is 0%, so the description must carry the parameter burden. It partially maps the 'chart' values by restating the enum and hints that a region is involved, but never mentions 'limit', gives no country code format (e.g. 'US'), and no defaults, leaving two of three parameters effectively 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?

States a specific resource (Steam store charts) with the exact scope ('current', 'for a region') and enumerates the four chart variants, which unambiguously separates it from siblings like search_games, game_details, and regional_prices. No explicit verb, but the read semantics are obvious from the phrasing.

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?

The description implies the use case (fetching store charts for a region) but gives no when-to-use vs. when-not guidance and never names an alternative among search_games, regional_prices, or game_news. An agent must infer the routing itself.

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