Skip to main content
Glama
Sign In
Steam Scout MCP

Steam Scout MCP

by cyanspearfitting4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

player_count

Read-onlyIdempotent

Fetch the current number of players in a Steam game by app ID to check real-time popularity and activity.

Instructions

Number of players currently in the game right now.

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

Input Schema

NameRequiredDescriptionDefault
app_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 the one behavioral fact not in annotations — the value is a real-time snapshot, not historical or peak — but says nothing about return shape (integer vs object) or whether the game must exist/is live.

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 short sentence with the key qualifier ('currently... right now') front-loaded and zero filler. It is efficient but so terse that it reads as under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a required identifier and no output schema, the description should state the return format (a plain integer count) and that app_id is a Steam-style app ID. Neither is present, leaving an agent to guess both the input format and what comes back.

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% and the single parameter app_id is never mentioned in the description, so an agent gets no signal that this takes a store application identifier rather than a name, slug, or internal ID. With one undocumented required param, the description needed to compensate and does not.

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 concrete resource and metric — the count of players currently in a game — which is unambiguous and not duplicated by any sibling (search_games, game_details, store_charts all cover different resources). The retrieval verb is implicit rather than stated, and no sibling is named as a contrast, 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?

The description gives no when-to-use guidance, no prerequisites, and no pointer to alternatives; it never says whether to call this alongside game_details or store_charts for a fuller picture. Usage can only be inferred from the phrase 'currently in the game right now'.

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