RuneScape Wiki MCP Server

Get Player Stats

get_player_stats

Read-onlyIdempotent

Retrieve RuneScape 3 hiscores for a player by username and game mode. For ironman or hardcore modes, report missing endpoint results clearly instead of returning normal-mode data.

Instructions

Get RS3 hiscores for a player. Normal mode works via Jagex index_lite. Ironman/hardcore use documented Jagex endpoints that currently return HTTP 404; the tool reports that clearly instead of falling back to normal data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gameMode`	No	Hiscores board (default: normal)	normal
`username`	Yes	Player username to lookup

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.1Oct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "experience": {
+        "description": "Skill experience",
+        "type": "integer"
+      },
+      "level": {
+        "description": "Skill level",
+        "type": "integer"
+      },
+      "rank": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "const": "Unranked"
+          }
+        ],
+        "description": "Hiscores rank, or the string Unranked"
+      }
+    },
+    "required": [
+      "rank",
+      "level",
+      "experience"
+    ],
+    "type": "object"
+  },
+  "description": "Map of RS3 skill name to hiscores row. Overall is included.",
+  "type": "object"
+}

First observedv1.1.0Aug 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower; the description adds a genuinely useful failure mode beyond them — ironman/hardcore return HTTP 404 and the tool surfaces that rather than silently falling back to normal data. It does not disclose rate limits or response shape, but the silent-fallback warning is the key behavioral fact.

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?

Two tight sentences: the core purpose first, then the mode-specific caveat. No filler, and the most important constraint (broken modes) is not buried.

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?

With an output schema present, return values need not be described, and the description covers the operational caveats an agent needs before calling. Nothing material is missing for a two-parameter read-only lookup.

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% (baseline 3), and the description goes beyond the enum labels by explaining what each mode means operationally (index_lite vs. alternate endpoints). That is real added meaning for the gameMode parameter rather than a restatement of the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get RS3 hiscores for a player'), which is immediately distinguishable from the item/GE/wiki-oriented siblings. An agent knows exactly what domain this tool covers without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear conditional guidance per game mode: normal works, ironman/hardcore hit currently-broken endpoints. It stops short of naming an alternative tool or an explicit 'use this instead of X' rule, but the mode-level context is enough to choose correctly.

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

Deploy Server