Wynncraft

Player

player

Read-onlyIdempotent

Fetch a Wynncraft player's stats by UUID or username: playtime, XP, guild, ranking, veteran status, and per-class totals.

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": {
      "uuid_or_username": "Technoblade"
    },
    "name": "player"
  }
}

Input Schema

Name	Required	Description	Default
`uuid_or_username`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "uuid_or_username": "Technoblade"
+  },
+  {
+    "uuid_or_username": "550e8400-e29b-41d4-a716-446655440000"
+  }
+]

changedOutput schema / (root)

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

First observedMay 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is provided. The description adds that it fetches stats and lists what stats, which is consistent with annotations. No contradictions, but minimal extra behavioral context beyond the annotations.

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 description is a single, well-structured sentence that clearly and concisely conveys the purpose. No unnecessary words.

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?

Given the tool's simplicity (one parameter, no nested objects), the presence of an output schema to document return values, and the annotations covering read-only, idempotent behavior, the description is complete enough for an AI agent to understand and invoke the tool correctly.

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?

The schema has 0% description coverage for the parameter, but the description clarifies that 'uuid_or_username' accepts either a UUID or a username. This adds meaning beyond the bare schema type definition.

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 description clearly states the tool fetches a Wynncraft player's stats by UUID or username, listing specific data fields (playtime, XP, guild, ranking, veteran status, per-class totals). This verb+resource+scope is specific and distinguishes it from sibling tools that fetch other entities like guild or items.

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 implies the tool is for retrieving player stats, providing clear context. However, it does not explicitly state when to use this over siblings like 'guild' or 'player_characters', nor does it provide exclusions or alternatives.

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.