Everloot: WoW Forever data

NPC page

npc_page

Read-onlyIdempotent

Returns one Forever NPC's page by NPC id: the agreed name, the agreed map pins, and the loot windows reported for it that are not yet in the drop rates. A name or pin needs 3 installs agreeing; a pin does not require a drop. No copied spawn list. Use it to name or place an NPC when you have its id, from a search_knowledge hit, a drop row or entity_relations; use vendor_page for what an NPC sells, item_page for one drop's rate, entity_relations for every typed link, and world_map_near for what stands around it. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "npcId": "<npcId>"
    },
    "name": "npc_page"
  }
}

Input Schema

Name	Required	Description	Default
`npcId`	Yes	The game's NPC id, from world_map_near, entity_relations or the extId of a search_knowledge hit of kind npc.

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.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / npcId / description

Previous value: -"NPC id."New value: +"The game's NPC id, from world_map_near, entity_relations or the extId of a search_knowledge hit of kind npc."

Changed1 schema field changedOct 21, 2026

addedOutput schema / properties / page / properties / pendingLoot

Added value: +{
+  "additionalProperties": false,
+  "description": "Loot windows reported but not yet in the rates. Absent when there are none.",
+  "properties": {
+    "reporters": {
+      "description": "Distinct reporters behind those windows.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "windows": {
+      "description": "Reported loot windows not yet in the rates.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "windows",
+    "reporters"
+  ],
+  "type": "object"
+}

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

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavioral context: data-agreement thresholds (three installs must agree), the rule that a pin does not require a drop, that no copied spawn list is included, the Everloot public-data provenance, and that missing data is reported explicitly rather than silently omitted.

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 content, then usage, then alternatives, then caveats — a sound ordering with no filler sentences. It is dense, packing several rules into semicolon-linked clauses, which is efficient but slightly harder to scan than discrete sentences.

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?

An output schema exists, so return shape needn't be spelled out, yet the description still tells the agent what categories of data come back and how trustworthy they are. For a single-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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% for the single npcId parameter, so the schema already carries validation and sourcing detail. The description only restates "by NPC id" and adds a loosely matching note about where ids come from, so the baseline 3 applies.

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 one Forever NPC's page by NPC id") and then enumerates what the page contains: agreed name, agreed map pins, and loot windows not yet in drop rates. It is clearly distinguishable from siblings like vendor_page and item_page, which the description names explicitly.

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?

Gives an explicit trigger ("Use it to name or place an NPC when you have its id") plus where the id comes from (a search_knowledge hit, a drop row, or entity_relations). It then routes four alternatives to their proper tools: vendor_page for sales, item_page for a single drop rate, entity_relations for typed links, world_map_near for surroundings.

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.