Everloot: WoW Forever data

How an item, NPC, spell or quest connects to others

entity_relations

Read-onlyIdempotent

Lists every typed relation of one entity, in both directions, grouped by relation. Player-observed relations (dropped by, sold by, reward from, located in) are listed where 3 installs agree, with the install count and last seen. Game-file relations (created by, reagent for, part of set, same icon) are found in game files, unconfirmed, with the build they came from. Ids are the game's own, as a page tool, a drop row or world_map_near gives them. Use it for where something comes from or what something drops, sells or rewards; use the page tools (item_page, npc_page, quest_page) for one entity's own facts, and world_map_near for what is near a place. Reads Everloot's public player data and the game-file relations of the current build.

Input Schema

Name	Required	Description	Default
`id`	Yes	The game's id for it, such as item 19019.
`rel`	No	Only this relation. Without it, every relation.
`kind`	Yes	What the id names. A zone is a UiMap id, as on /map.
`limit`	No	Most lines per relation, 1 to 100, default 25.
`direction`	No	from: what this entity points to (an item's sources). to: what points at it (what an NPC drops). Default both.	both

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.
`page`	No
`reason`	No	Why nothing was read, when connected is false.
`dataAsOf`	Yes	The corpus snapshot time, or null when unrecorded.
`connected`	Yes	False when no corpus was read; the page is then absent, which is not a measured zero.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / limit / description

Previous value: -"Most lines per relation."New value: +"Most lines per relation, 1 to 100, default 25."

changedInput schema / properties / rel / description

Previous value: -"Only this relation."New value: +"Only this relation. Without it, every relation."

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.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real provenance context beyond them: player-observed relations require 3 agreeing installs and carry install count and last-seen, while game-file relations are unconfirmed and tied to a specific build. It does not discuss result volume beyond what the limit parameter implies, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Opening sentence is front-loaded with the core action and output shape; subsequent sentences add provenance, id convention, and sibling routing in a logical order with no filler or repetition.

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?

With an output schema present the description needn't explain return values, and it covers purpose, provenance, id conventions, and alternatives. Minor gap: it doesn't hint at how relation groups are ordered or what happens when no relations meet the 3-install threshold.

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 coverage is 100%, so kind, id, rel, limit and direction are all documented in the schema including the from/to semantics. The description only adds that ids are the game's own as returned by page tools or world_map_near, which is a small but useful clarification — baseline 3 is appropriate.

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 plus scope: 'Lists every typed relation of one entity, in both directions, grouped by relation.' It immediately makes clear it is a relation graph lookup, not an entity fact lookup, which separates it from item_page/npc_page without needing 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?

States the triggering question ('where something comes from or what something drops, sells or rewards'), then names the excluded alternatives and when to prefer them: page tools for one entity's own facts, world_map_near for proximity. Explicit when-to-use and when-not-to-use routing.

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.