Skip to main content
Glama

get_game_stats

Retrieve community statistics for a game, including owner status, completion rates, wishlist counts, average playtime, and rating distribution.

Instructions

Community stats for a game: owners by status and completion, wishlist count, playtime averages, and rating distribution.

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": {
      "slug": "<slug>"
    },
    "name": "get_game_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Stats' plus the enumeration of returned metrics implies a safe read operation, but the description never states read-only/destructive behavior, authentication or privacy scoping requirements, or rate-limit behavior — gaps that matter with zero annotation coverage.

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 that names the scope first and then lists the metric families. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return values need not be explained, and the tool is structurally simple with one required parameter. However, with no annotations and no parameter documentation anywhere, the definition leaves the identifier format and the read-only/safety profile entirely unstated.

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% for the single required parameter 'slug', and the description never mentions it. It does not clarify whether the slug is a game slug, whether it is the same identifier used by get_game, or whether numeric IDs are accepted, leaving the agent to guess the identifier format.

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?

Uses a specific verb+resource framing ('Community stats for a game') and enumerates the exact metric families returned, which distinguishes it from get_user_stats and get_game. It does not name a sibling explicitly, so differentiation relies on the agent inferring 'community' vs 'user'.

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 or when-not-to-use guidance is given. The word 'community' implicitly signals it is the aggregate counterpart to user-level stats, but the agent must infer that get_user_stats or get_game is the alternative for personal or descriptive data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.