entity_relations
How an item, NPC, spell or quest connects to others
Every typed relation of one entity, both directions: dropped by, sold by, reward from, located in (player-observed, listed where 3 installs agree, with the install count and last seen), and created by, reagent for, part of set, same icon (found in game files, unconfirmed, with the build they came from). Ids are the game's own. Reads Everloot's current authorized public corpus and the committed client layer.
Parameters#
kindone of: item, spell, npc, object, quest, zone, item_set, icon, skillrequired- What the id names. A zone is a UiMap id, as on /map.
idinteger, 1 to 9007199254740991required- The game's id for it, such as item 19019.
relone of: dropped_by, sold_by, reward_from, located_in, created_by, reagent_for, part_of_set, same_icon, in_skill_line- Only this relation.
directionone of: from, to, both- from: what this entity points to (an item's sources). to: what points at it (what an NPC drops). Default both.
limitinteger, 1 to 100, default 25- Most lines per relation.
The answer#
Text for the assistant to read, and structuredContent with these top-level fields. The JSON Schema is at /schema/mcp/entity_relations.json.
connectedbooleanrequired- False when no corpus was read; the page is then absent, which is not a measured zero.
dataAsOfstring, or nullrequired- The corpus snapshot time, or null when unrecorded.
reasonstring- Why nothing was read, when connected is false.
pageobject- No description.
Without an MCP client#
The same answer is a GET away: /api/tools/entity_relations with the arguments in the query string. See the endpoint and the recipe.