Everloot: WoW Forever data

WoW: Forever addons and open-source projects

ecosystem_projects

Read-onlyIdempotent

Lists the Forever addons and tools in the community registry, with a board ranking: most installed, rising, most active, freshest release or best maintained. Each project shows its GitHub repository, stars, latest release, last commit, whether its .toc declares a Forever interface number, and installs from Everloot uploads (counted from 3 installs; a missing count means not counted, not zero). Projects are ranked, never people. GitHub facts carry the time they were refreshed. Use it for which Forever addons exist and how maintained they are; use everloot_plan for Everloot's own features, and recent_changes for Blizzard's posts. limit caps the projects listed.

Input Schema

Name	Required	Description	Default
`board`	No	installed, rising, active, release, maintained, or all (default, A to Z).	all
`limit`	No	Most projects listed, 1 to 25, default 10.
`forever_ready_only`	No	Only projects whose .toc lists a Forever interface number. Default false.

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.
`board`	Yes
`forever`	Yes	What Forever-ready compares each .toc with, derived from the build's version and not yet confirmed in the client.
`projects`	Yes
`connected`	Yes	False when the tracker is not connected: the list is then not a measured zero.
`refreshedAt`	Yes	When the GitHub facts were last refreshed.
`installsAvailable`	Yes	False when install counts could not be read: a null count then means unknown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

changedInput schema / properties / board / description

Previous value: -"installed, rising, active, release, maintained, or all (A to Z)."New value: +"installed, rising, active, release, maintained, or all (default, A to Z)."

changedInput schema / properties / forever_ready_only / description

Previous value: -"Only projects whose .toc lists a Forever interface number."New value: +"Only projects whose .toc lists a Forever interface number. Default false."

changedInput schema / properties / limit / description

Previous value: -"Most projects listed, 1 to 25."New value: +"Most projects listed, 1 to 25, default 10."

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

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, closed-world), yet the description adds substantive data semantics: the five ranking boards, the install-counting rule (counted from 3 installs; missing means not counted, not zero), the "projects are ranked, never people" caveat, and GitHub fact freshness timestamps. These are non-obvious behaviors an agent could not recover 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?

Purpose and board list are front-loaded, then details, then sibling routing, then the limit note — a sensible order. It is dense but every clause carries information; only the closing "limit caps the projects listed" is slightly redundant with the schema.

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 an output schema present, the description needn't explain return shape, and annotations cover safety; the remaining burden is scope, ranking semantics, and data caveats, all of which are covered. Nothing an agent needs to select or call this tool correctly is missing.

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, but the description expands the enum values with plain-language meaning ("most installed, rising, most active, freshest release or best maintained") and restates limit's capping role plus the .toc interface-number condition behind forever_ready_only. It adds genuine interpretation beyond the bare enum labels.

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?

Opens with a specific verb and resource ("Lists the Forever addons and tools in the community registry") plus the ranking dimension, and immediately distinguishes itself from everloot_plan and recent_changes by name. An agent can tell what this returns without opening the 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 ("which Forever addons exist and how maintained they are") and routes the agent to two named siblings with the conditions that select them: everloot_plan for Everloot's own features, recent_changes for Blizzard's posts. Nothing is left to inference.

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.