Skip to main content
Glama

Wynncraft Player

wynncraft_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": "wynncraft_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuid_or_usernameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld access, so the safety profile is covered. The description adds the retrievable field set beyond that, but says nothing about behavior for unknown players, lookup failures, or identifier case sensitivity.

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?

One front-loaded sentence with the resource first and the field list after; no filler. The field enumeration is partly redundant with the existing output schema, which costs it the top mark.

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?

A one-parameter read tool with an output schema and full annotations needs little more, and the description covers the resource and accepted identifier forms. Only ambiguity handling for unresolved players is left unaddressed, a minor gap at this complexity.

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 0% and the bare property is only typed as string, so the description carries the burden of explaining that the single argument accepts either a UUID or a username — a meaningful addition the schema text does not make. It stops short of specifying format constraints or precedence when the value is ambiguous.

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?

"Fetch a Wynncraft player's stats" gives a specific verb and resource, and enumerates the domains returned (playtime, XP, guild, ranking, veteran status, per-class totals). It is clear without opening the schema, but it never differentiates itself from near-neighbors like player_characters or guild, leaving an agent to guess at the boundary.

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 "by UUID or username" phrasing implies when the tool applies, but there is no explicit when-to-use, no exclusions, and no named alternative. An agent must infer that player_characters covers per-character detail rather than reading it here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.