Everloot: WoW Forever data

Recent official changes for WoW: Forever

recent_changes

Read-onlyIdempotent

Returns the newest official changes for WoW: Forever, newest first: Blizzard blue posts (title, author, time, a short excerpt and the link to the original), hotfix posts, and new game builds. Excerpts only: Blizzard's post text is Blizzard's; full posts are available at their source URLs. A build's time is when Everloot first saw it, not Blizzard's release time. Use it for what Blizzard changed or posted lately; use answer_sources for lore and game facts, and ecosystem_projects for community addons. filter picks one kind; limit caps the entries.

Input Schema

Name	Required	Description	Default
`game`	No	forever or classic. Without it, both.
`limit`	No	Most entries, 1 to 25, default 10, newest first.
`filter`	No	posts (blue posts), hotfixes, builds, or all (default).	all

Output Schema

Name	Required	Description
`url`	No	The changes page on everloot.app with the same filter, absolute.
`entries`	Yes
`connected`	Yes	False when the timeline is not connected: the list is then not a measured zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

changedInput schema / properties / filter / description

Previous value: -"posts (blue posts), hotfixes, builds, or all."New value: +"posts (blue posts), hotfixes, builds, or all (default)."

changedInput schema / properties / game / description

Previous value: -"Narrow to one game."New value: +"forever or classic. Without it, both."

changedInput schema / properties / limit / description

Previous value: -"Most entries, 1 to 25, newest first."New value: +"Most entries, 1 to 25, default 10, newest first."

Changed1 schema field changedNov 3, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Most entries, 1 to 25, newest first."
```

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / url

Added value: +{
+  "description": "The changes page on everloot.app with the same filter, absolute.",
+  "type": "string"
+}

Changed5 schema fields changedOct 20, 2026

addedOutput schema / properties / entries / items / properties / postNumber

Added value: +{
+  "description": "Forum posts: the post's number in its thread; 1 opened the thread.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / entries / items / properties / region

Added value: +{
+  "description": "Forum posts: the US or EU English WoW forum.",
+  "enum": [
+    "us",
+    "eu"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / entries / items / properties / startedThread

Added value: +{
+  "description": "Forum posts: true when this Blizzard post opened the thread, false for a reply.",
+  "type": "boolean"
+}

addedOutput schema / properties / entries / items / properties / topicId

Added value: +{
+  "description": "Forum posts: the thread's topic id on that forum. Region and topic id together name one thread.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / entries / items / properties / topicSlug
```
Added value: +{
+  "type": "string"
+}
```

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a safe, idempotent read, so the description focuses on genuinely additive behavior: results are truncated excerpts with source links, and a build's timestamp is Everloot's first-seen time rather than Blizzard's release time. That timestamp caveat is the kind of subtlety an agent would otherwise misinterpret.

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?

Front-loaded with the return contents and ordering, then caveats, then usage routing — a sensible priority order with no filler. The closing sentence about filter and limit is somewhat redundant with a fully documented schema, costing a bit of tightness.

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 annotations and an output schema present, the description still covers what an agent needs: content types, ordering, the excerpt-only constraint, the build-time caveat, and sibling routing. Nothing material is left to inference for a three-parameter read tool.

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

Parameters3/5

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

Schema description coverage is 100% and two of three parameters are enums the schema fully documents, so the baseline is 3. The description's 'filter picks one kind; limit caps the entries' restates the schema rather than adding format or interaction detail, and the game parameter is not mentioned at all.

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?

States a specific verb and resource ('Returns the newest official changes for WoW: Forever') and enumerates the three content types returned: blue posts, hotfix posts, and new game builds. That enumeration makes it distinguishable from lore/knowledge siblings 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?

Explicitly states the use case ('what Blizzard changed or posted lately') and names two alternatives with the conditions that select them: answer_sources for lore and game facts, ecosystem_projects for community addons. Both when-to-use and when-not-to-use are covered.

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.