Skip to main content
Glama

get_player_stats

Read-only

Retrieve complete CS2 performance statistics for one player in a match, including rating, ADR, KAST, opening duels, trades, multi-kills, clutches, utility, and CT/T splits.

Instructions

Every stat of one player: rating, ADR, KAST, opening duels, trades, multi-kills, clutches, utility, per-weapon kills, CT/T split.

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": {
      "match_id": "<match_id>",
      "player": "<player>"
    },
    "name": "get_player_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYesSteamID or player name.
match_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds scope information by enumerating the returned stat families, but says nothing about failure behavior (unknown player name, missing match) or that results are scoped to one specific match.

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?

A single front-loaded sentence with no filler; each stat name carries informational weight. The enumerated list is slightly catalogue-like but serves to establish coverage.

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 the description does not need to enumerate return values — yet that is most of what it does, duplicating structured data. The genuinely useful gaps (match scoping, player-identifier resolution) are left unaddressed, though annotations and schema cover enough that the omission is not crippling.

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 only 50%: player is documented as 'SteamID or player name' but match_id has no description at all, and the description text does not compensate for that. Worse, 'Every stat of one player' never says the stats are scoped to the required match_id, leaving a real ambiguity about whether these are career or per-match numbers.

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?

Names a specific resource (one player's stats) and enumerates the breadth of metrics covered — rating, ADR, KAST, clutches, CT/T split — so an agent can tell this is a deep per-player stats dump rather than a summary. It never distinguishes itself from the sibling get_player_profile, which plausibly overlaps.

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?

Contains no when-to-use or when-not-to-use guidance, no mention of the closest sibling get_player_profile, and no stated prerequisites. The agent must infer usage entirely from the tool name and the stat list.

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