Everloot: WoW Forever data

What is near a place on the map

world_map_near

Read-onlyIdempotent

Lists the entrances, NPCs, vendors and treasures near a spot, nearest first, with straight-line distances in yards. Give a zone (name or map id) with x and y from 0 to 100, or an NPC id to start from where that NPC stands. Entrances come from the game files; one is confirmed once 3 installs zoned in from it. NPCs, vendors and treasures are player-observed and listed only where 3 installs agree on the position. Zones the files hold back as possibly unreleased are not offered. Use it for what is near a spot; use npc_page, vendor_page or entity_relations for one entity's own facts. Reads Everloot's public player data when connected.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "world_map_near"
  }
}

Input Schema

Name	Required	Description
`x`	No	Across the zone map, 0 (west) to 100 (east).
`y`	No	Down the zone map, 0 (north) to 100 (south).
`zone`	No	Zone name or map id, such as Elwynn Forest or 1429. Needs x and y.
`limit`	No	Most results per list, 1 to 20, default 5.
`npcId`	No	Start from this NPC's agreed position instead of a zone and x, y.
`radius`	No	Search radius in yards, up to 5000, default 500.

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 results per list."New value: +"Most results per list, 1 to 20, default 5."

changedInput schema / properties / radius / description

Previous value: -"Search radius in yards."New value: +"Search radius in yards, up to 5000, default 500."

Changed3 schema fields changedOct 21, 2026

changedOutput schema / properties / page / properties / entrances / description

Previous value: -"From the game files, found in game files, unconfirmed. Nearest first."New value: +"From the game files, found in game files, unconfirmed unless confirmed is set. Nearest first."

addedOutput schema / properties / page / properties / entrances / items / properties / confirmed

Added value: +{
+  "description": "Installs that zoned in from this entrance, once 3 agree on it; absent until then.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / page / properties / treasures

Added value: +{
+  "description": "Game objects players saw on the minimap at their own position, such as treasure chests; a pin needs 3 installs at one spot.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "mapId": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "objectId": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "reporters": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      },
+      "yards": {
+        "type": "number"
+      },
+      "zoneName": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "objectId",
+      "name",
+      "mapId",
+      "zoneName",
+      "x",
+      "y",
+      "yards",
+      "reporters"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

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?

Goes well beyond the annotations (which already cover read-only, idempotent, non-destructive). It discloses data provenance and thresholds: entrances from game files with a 3-install confirmation, player-observed NPCs/vendors/treasures requiring 3-install agreement, suppression of possibly-unreleased zones, and that public player data is read when connected. These are behavioral facts an agent could not infer 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?

Front-loaded with the core capability and tight throughout, but slightly redundant at the close, where 'Use it for what is near a spot' restates the title's premise before naming alternatives. Every other sentence carries new information.

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, return-shape explanation is unnecessary, and the description covers the remaining gaps: anchor modes, coordinate convention, provenance and reliability thresholds, and sibling routing. Nothing needed to invoke it 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 baseline is 3. The description adds the additive semantics the schema only hints at: zone+x+y and npcId are alternative anchors ('instead of'), and the 0-100 coordinate convention is reinforced. It does not explain the interaction between radius/limit and each list, so it stops short of a 5.

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?

Names a specific verb and resource ('Lists the entrances, NPCs, vendors and treasures near a spot'), states ordering ('nearest first') and units ('straight-line distances in yards'). An agent can distinguish this from npc_page or vendor_page without opening either 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?

Gives both positive and negative guidance plus named alternatives: 'Use it for what is near a spot; use npc_page, vendor_page or entity_relations for one entity's own facts.' It also spells out the two valid input modes (zone+x+y or npcId), which is exactly the decision an agent must make before calling.

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.