rust.wiki

Player-count history for one server

get_server_player_history

Read-onlyIdempotent

Player-count history for one server. The per-poll player_count/queued_count readings behind the server page's 24-hour chart, oldest first, as points of {t, players, queued}. One reading lands per poll cycle (roughly hourly); when the window holds more than 500 readings they are averaged into equal time buckets (resolution_seconds, null when the points are raw) so a response never exceeds 500 points. Also peak_players, avg_players and point_count. A server that has never answered a poll has an empty series. Cached for five minutes.

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": {
      "server_id": "<server_id>"
    },
    "name": "get_server_player_history"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	How many days back to return (1-30). Snapshots are pruned nightly to the configured retention window (7 days by default - see `snapshot_retention_days` on `/servers/stats`), so longer ranges come back only as far as the table holds.
`server_id`	Yes	The server's numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare a safe read, and the description adds substantial context beyond them: one reading per poll cycle (~hourly), a hard 500-point cap with equal-bucket averaging and a resolution_seconds signal for downsampled results, oldest-first ordering, empty series for never-polled servers, and a five-minute cache. That is exactly the behavioral detail an agent needs to interpret the payload.

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-loads the purpose, then the return shape, then edge cases and caching — a logical order with no filler. It is dense in places (the bucketing sentence is long) but every clause carries operational value.

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

Completeness5/5

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

There is no output schema, yet the description fully specifies the response: `points` of `{t, players, queued}`, `resolution_seconds` nullability, `peak_players`, `avg_players`, and `point_count`, plus the empty-series case. Nothing an agent needs to call or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: it explains that a reading lands per poll cycle, so `days` translates into roughly 24 points per day unless bucketing kicks in. The server_id parameter is left to the schema, which is fine at full coverage.

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+resource ('Player-count history for one server') and pins down exactly which readings are returned (per-poll player_count/queued_count behind the 24-hour chart). It is distinguishable from sibling get_server_stats and get_player_stats by scope, though it never names those alternatives explicitly.

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?

The 'days' back parameter and the chart framing imply when to reach for this tool, but there is no explicit when-to-use/when-not guidance or pointer to get_server_stats or get_player_stats for current-state vs history queries. Usage must be inferred from the wording.

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

All rust.wiki tools Inspect

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

Need Help?