Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_players

Fetch the current concurrent-player count for a Steam app by its numeric appid. Returns player_count with source_url, or 404 when no data.

Instructions

Get the current concurrent-player count for a Steam app. Returns the current number of concurrent players for a Steam app, given its numeric appid such as 570. The response has appid, player_count and a source_url. An app with no player-count data returns 404.

Input Schema

NameRequiredDescriptionDefault
appidYesNumeric Steam app id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return fields (appid, player_count, source_url) and the 404 behavior for apps without data. It does not mention auth or rate limits, so it stops short of a 5.

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?

Front-loaded and suitably sized, but the first two sentences partially repeat the same idea ("current concurrent-player count" vs "current number of concurrent players"), a small redundancy that keeps it from a 5.

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

Completeness4/5

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

For a simple one-parameter tool with no output schema, the description covers the return fields and error case adequately. Slightly more context (e.g. data freshness) would make it fully complete.

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 100% for the single appid parameter, so the schema already documents it. The description adds only marginal value by restating it as numeric and giving the example `570`, which is the expected baseline here.

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 verb ("Get") and resource ("current concurrent-player count for a Steam app") and gives a concrete example appid. It is clear what the tool returns, but it does not distinguish itself from the overlapping sibling steam_charts_concurrent, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use, when-not-to-use, or named alternatives are given (e.g. vs steam_charts_concurrent). Usage is only implied by the resource description, which lands at the minimum-viable level.

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