Skip to main content
Glama
Sign In

RuneScape Wiki MCP: GE Analytics & References

by io.github.birdwell
OverviewDiscussionsAdmin

Get Player Stats

get_player_stats
Read-onlyIdempotent

Read an RS3 player's published hiscores ranks, levels and experience, including Overall. Use search_wiki for training guides rather than player data.

  • username is the literal in-game display name, including spaces; the server URL-encodes it. gameMode chooses a separate leaderboard, not a filter on normal stats. Omit it for normal mode.

  • Normal, ironman and hardcore boards are supported. A player absent from the selected board returns a 404 tool error; the tool never substitutes another board. Unranked skills use rank Unranked; unavailable level/XP becomes 0.

  • No login, account changes or local cache. HTTP shares a default 60 requests/IP/minute budget; honor Retry-After on 429.

Input Schema

NameRequiredDescriptionDefault
gameModeNoHiscores board (default: normal)normal
usernameYesPlayer username to lookup

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations it discloses concrete operational traits: a 404 tool error when a player is absent from the selected board, no silent cross-board substitution, 'Unranked' rank and 0 for unavailable level/XP, no login/account changes/local cache, a 60 requests/IP/minute shared budget, and Retry-After handling on 429. This is exactly the context annotations cannot carry.

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?

The capability and the sibling routing are front-loaded in the first two sentences, then the remaining lines are grouped by concern (parameters, board semantics/errors, auth and rate limits). No sentence is filler, and the dense bullets are scannable rather than rambling.

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 only two parameters, an output schema already documenting return values, and annotations covering safety, the description adds the missing edges: failure mode, sentinel values, board isolation, and rate-limit behavior. Nothing an agent needs to call this correctly is absent.

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

Parameters5/5

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

Schema coverage is already 100% (baseline 3), and the description still adds real meaning: username is the literal in-game display name including spaces with server-side URL-encoding, and gameMode selects a separate leaderboard rather than filtering normal stats. Both clarifications prevent plausible misuse that the terse schema descriptions do not.

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?

The first sentence names a specific verb and resource ('Read an RS3 player's published hiscores ranks, levels and experience, including Overall') and immediately distinguishes itself from the nearest sibling by deferring training guides to search_wiki. An agent can identify the tool's job without inspecting 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 Guidelines5/5

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

It explicitly routes the agent away from this tool ('Use search_wiki for training guides rather than player data') and gives a selection rule for the one optional parameter ('Omit it for normal mode'). When-to-use, when-not-to-use, and the alternative are all stated.

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

All RuneScape Wiki MCP: GE Analytics & References 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