Skip to main content
Glama
Sign In

rust.wiki

by wiki.rust
OverviewDiscussionsAdmin

Player profile, Rust stats and achievements

get_player_stats
Read-onlyIdempotent

Player profile, Rust stats and achievements. Profile summary (name, avatar, country, Steam level, account age), VAC/game bans, Rust playtime, every Rust stat Steam exposes grouped into Combat / Animals & NPCs / How you died / Gathering & loot / Building / Travel / Life on the island / Fishing / Music / Everything else, six headline figures (kills, deaths, K/D, headshots, bullet and arrow accuracy), and all 116 achievements with unlock dates. stats_private is true when the profile hides game details, in which case groups and achievements are empty.

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

Input Schema

NameRequiredDescriptionDefault
steamidYes17-digit SteamID64. Use /players/resolve for URLs and vanity names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. Beyond that, the description adds an important behavioral edge case: when `stats_private` is true, `groups` and `achievements` are empty. This is meaningful context that helps an agent interpret partial results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description becomes a long enumeration of stat categories, headline figures, and achievement count. That detail is useful because there is no output schema, but it is denser and less structured than ideal.

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?

With no output schema, the description does substantial work by listing what is returned: profile summary, bans, playtime, grouped stats, headline figures, achievements, and private-profile behavior. It is nearly complete for caller needs, though it does not describe output shape or handling of invalid SteamIDs.

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?

There is one required parameter, and schema description coverage is 100%, so the schema fully documents the required SteamID64 and even points to a resolve path for URLs or vanity names. The description itself does not add parameter guidance beyond what the schema already provides, so the baseline of 3 is appropriate.

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 description clearly identifies the resource: a player's Steam/Rust profile, stats, bans, and achievements. It is more specific than the tool name alone, but it does not distinguish this tool from nearby siblings such as resolve_steam_profile or get_server_player_history.

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?

There is no explicit guidance on when to use this tool versus alternatives. The implied use is retrieving a player's full profile and Rust stats, but no exclusions, prerequisites, or sibling routing are provided in the description.

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

All rust.wiki toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources