Everloot: WoW Forever data

Talent trees for one class

talent_tree

Read-onlyIdempotent

Returns the WoW: Forever talent trees of one class from the game files (found in game files, unconfirmed, with the build): every node with its talents, ranks, grid position, prerequisites and row gate, plus the levels talent points arrive at. Node ids are the ids a share code names. Use it to read or explain a class's trees; use talent_plan to decode a share code against them, and class_races for which races can be the class. Narrow to one tree by name; without it the answer holds every node of every tree. With builds, the answer also lists the Everloot team's published starter builds for the class, each labelled as the team's and not observed, with its share code and page. The answer links the calculator.

Input Schema

Name	Required	Description
`tree`	No	One tree by name, such as Arcane. Without it, every tree.
`class`	Yes	Class slug, such as mage.
`builds`	No	Also list the Everloot team's starter builds for the class, with share codes. They are the team's, not observed.

Output Schema

Name	Required	Description
`url`	No	The everloot.app page that shows this answer, absolute. Absent when there is no such page or it would be empty.
`build`	Yes	The game build the trees were read from.
`class`	Yes
`label`	Yes
`nodes`	Yes
`trees`	Yes
`credit`	Yes
`points`	Yes
`specId`	Yes	The client's spec id, or 0 when unknown.
`className`	Yes
`starterBuilds`	No	With builds: the team's published starter builds for the class (and tree), by name. Empty when none is published.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026
- changedInput schema / properties / class / description
```
Previous value: -"Class slug."New value: +"Class slug, such as mage."
```

Changed2 schema fields changedNov 4, 2026

addedInput schema / properties / builds

Added value: +{
+  "default": false,
+  "description": "Also list the Everloot team's starter builds for the class, with share codes. They are the team's, not observed.",
+  "type": "boolean"
+}

addedOutput schema / properties / starterBuilds

Added value: +{
+  "description": "With builds: the team's published starter builds for the class (and tree), by name. Empty when none is published.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "build": {
+        "description": "The game build the code was made on.",
+        "type": "string"
+      },
+      "label": {
+        "const": "Everloot team starter build, not observed",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "points": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "purpose": {
+        "enum": [
+          "leveling",
+          "dungeon",
+          "raid",
+          "pvp"
+        ],
+        "type": "string"
+      },
+      "shareCode": {
+        "description": "Reads with talent_plan.",
+        "type": "string"
+      },
+      "tree": {
+        "description": "The tree the build leans on.",
+        "type": "string"
+      },
+      "url": {
+        "description": "The shared build page.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "purpose",
+      "tree",
+      "shareCode",
+      "points",
+      "build",
+      "url",
+      "label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / url

Added value: +{
+  "description": "The everloot.app page that shows this answer, absolute. Absent when there is no such page or it would be empty.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the description spends its space on genuinely new behavior: data provenance and an explicit reliability caveat ('found in game files, unconfirmed, with the build'), the id-namespace guarantee that node ids match share-code ids, and the side effect of builds=true adding the Everloot team's starter builds explicitly labelled as the team's and not observed. That is meaningful context an agent could not infer from structured fields.

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?

It is a single front-loaded paragraph where scope and routing come first, and every clause carries information. The parenthetical '(found in game files, unconfirmed, with the build)' is awkwardly redundant with 'from the game files', and the builds labelling is stated twice (description and schema), costing a point.

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?

An output schema exists, yet the description still characterizes the return shape enough to plan around it (node fields, level thresholds, linked calculator, optional builds section). Combined with explicit sibling routing and the unconfirmed-data caveat, an agent has everything needed to call this 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?

Schema coverage is 100%, so the baseline is 3; the description still adds value by explaining what builds actually returns beyond the boolean (share code and page, and the team-not-observed caveat) and by clarifying the tree narrowing behavior. The class parameter is only restated, which keeps it from a 5.

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 opens with a specific verb and resource: it 'Returns the WoW: Forever talent trees of one class from the game files', and it enumerates the payload (nodes, talents, ranks, grid position, prerequisites, row gate, level thresholds). It also names the sibling tools it is not (talent_plan, class_races), so an agent can route without opening any 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 gives explicit when-to-use guidance ('read or explain a class's trees') and explicit alternatives for adjacent tasks: talent_plan for decoding a share code, class_races for race eligibility. It also states the scoping decision for the optional tree parameter ('Narrow to one tree by name; without it the answer holds every node of every tree').

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

All Everloot: WoW Forever data 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.