Wynncraft

Leaderboard

leaderboard

Read-onlyIdempotent

Fetch a Wynncraft leaderboard by type; returns ranked entries up to resultLimit. type must be one of the API's leaderboard ids — e.g. 'combatGlobalLevel', 'guildLevel', 'warsCompletion', 'playerContent' — NOT a generic word like 'overall' or 'level', which the API rejects with InvalidLeaderboardType.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "combatGlobalLevel"
    },
    "name": "leaderboard"
  }
}

Input Schema

Name	Required	Description	Default
`type`	Yes	Leaderboard id, e.g. combatGlobalLevel, guildLevel, warsCompletion, playerContent
`resultLimit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "type": "overall"
-  },
-  {
-    "resultLimit": 50,
-    "type": "level"
-  }
-]New value: +[
+  {
+    "type": "combatGlobalLevel"
+  },
+  {
+    "resultLimit": 50,
+    "type": "guildLevel"
+  }
+]

addedInput schema / properties / type / description

Added value: +"Leaderboard id, e.g. combatGlobalLevel, guildLevel, warsCompletion, playerContent"

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "type": "overall"
+  },
+  {
+    "resultLimit": 50,
+    "type": "level"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Leaderboard data from Wynncraft API",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing the return shape ('ranked entries up to resultLimit') and the failure mode (InvalidLeaderboardType on bad input), though it says nothing about pagination or defaults.

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 sentences with zero waste. Purpose and return behavior are front-loaded, and the critical input constraint follows immediately, so every clause earns its place.

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?

Output schema exists, so return values need no prose, and annotations cover safety. The description covers the type constraint and resultLimit semantics, though it omits a default or range for resultLimit, leaving a minor gap for a simple two-parameter tool.

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 only 50% (resultLimit is undocumented in the schema), but the description compensates: it gives semantic meaning to 'type' via valid and invalid examples, and explains resultLimit as the cap on returned entries. This goes beyond the structured schema for both parameters.

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 and resource: 'Fetch a Wynncraft leaderboard by type', and the return behavior 'ranked entries up to resultLimit'. The resource is unique among siblings (no other tool handles leaderboards), so differentiation is implicit rather than stated, keeping it just below a 5.

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?

Provides clear context for correct invocation, including the when-not case that 'type' must be an API id and not a generic word like 'overall' or 'level'. It does not, however, address when to choose this tool versus alternatives, so it stops short of full when/when-not guidance.

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

All Wynncraft 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.