Skip to content
everloot

coverage

Database coverage by zone, type and field

How much of WoW: Forever's database is settled or confirmed, and which reported fields need more agreeing installs. The same counts and reported lists as https://everloot.app/database/coverage, as text, per zone, per type and per field: coverage = settled / expected, with confirmed / expected beside it; the denominator is max(expected, observed). A player-reported fact needs three agreeing installs to be public. Only public report identifiers and game-file facts are listed, never unconfirmed values, baseline rows, names or ids, or player names. Every answer states its scope, measurement method, data date and install counts; unknown values are [?]. Zone and type are optional; omitted filters cover all released zones and all types.

Parameters#

zoneinteger, 1 or more
Released UiMap zone id, such as 1429 for Elwynn Forest. Omit for all released zones.
typeone of: quests, npcs, pins, vendors, drops, rares, entrances, bosses, treasures
Coverage type. Omit for all types.

The answer#

Text for the assistant to read. The JSON Schema is at /schema/mcp/coverage.json.

Without an MCP client#

The same answer is a GET away: /api/tools/coverage with the arguments in the query string. See the endpoint and the recipe.

Call it
curl https://everloot.app/mcp/public \
  --header "content-type: application/json" \
  --header "accept: application/json, text/event-stream" \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"coverage","arguments":{"zone":1429,"type":"quests"}}}'

Arguments show the shape of a call; check the parameters for real values.