Skip to main content
Glama

get_player_profile

Read-only

Fetches a CS2 player's aggregated match profile—wins, K/D/A, ADR, KAST, rating, highlights, rivalries, and chat stats—with optional date or match filters; omit filters to include all matches.

Instructions

One player across matches: matches, wins, K/D/A, ADR, KAST and rating (weighted by rounds), HS%, clutches, opening duels, multi-kills, best plays (highlight ids and scores), fails by kind, nemesis and favourite victim, chat numbers and the last matches. No filter = every match he played.

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

Input Schema

NameRequiredDescriptionDefault
nightNoOne night, YYYY-MM-DD (the evening it started; games after midnight belong to the night before). See list_nights.
sinceNoOnly matches played at or after this ISO 8601 moment.
untilNoOnly matches played before this ISO 8601 moment.
playerYesSteamID or player name.
match_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety is covered. The description adds genuinely useful behavior: results are aggregated across matches, rating is weighted by rounds, and an unfiltered call returns the entire match history. It does not say how match_id interacts with the aggregation or whether the profile is computed on the fly.

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?

The scope statement is front-loaded and the sentence is compact, but the metric enumeration is a long comma-chained run-on that is largely redundant given an output schema exists. Tightening the metric list would improve it without losing meaning.

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 spelling out every returned metric is wasted effort while the filter parameters (especially match_id and the night vs. since/until relationship) go unexplained. For a 5-parameter aggregation tool the description is adequate but leaves real gaps.

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 coverage is 80%, so the schema itself documents night, since, until and player. The description only alludes to filters via 'No filter = every match he played' and never explains match_id (presumably restricting to a single match) or how since/until interact with night.

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?

The fragment 'One player across matches' plus a long enumeration of metrics makes clear this returns an aggregated per-player profile. Scope (single player, multiple matches) is well defined, but there is no verb and no differentiation from the sibling get_player_stats, so an agent cannot tell the two apart without opening schemas.

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 only usage-relevant sentence is 'No filter = every match he played', which describes default behavior rather than when to choose this tool. There is no guidance on when to prefer get_player_stats, get_player_profile vs. list_matches, or when the night/since/until/match_id filters should be applied.

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