Everloot: WoW Forever data

What is near a place on the map

world_map_near

Read-only

Entrances, NPCs and vendors 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 and are unconfirmed. NPCs and vendors are player-observed and listed only where 3 installs agree on the position. Zones the files hold back as possibly unreleased are not offered. Game objects are not listed: no public record gives them a position. Reads Everloot's current authorized public corpus when connected.

Input Schema

TableJSON 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.
`npcId`	No	Start from this NPC's agreed position instead of a zone and x, y.
`radius`	No	Search radius in yards.

Output Schema

TableJSON Schema

Name	Required	Description
`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.

First observedOct 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark this as a safe read-only operation, and the description adds substantial behavioral context beyond them: provenance and confirmation levels for each entity type, the three-install agreement rule, unavailable unreleased zones, missing game objects, and the connected public corpus.

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?

The description is front-loaded with the result type and ordering, then moves efficiently through invocation, provenance, exclusions, and data source. Every sentence contributes actionable context.

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?

For a six-parameter read-only lookup with an output schema, the description is complete: it covers input modes, distance semantics, data reliability, exclusions, and the connected data source.

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 the schema documents the parameters in detail. The description still adds useful invocation semantics by presenting zone-plus-coordinates and NPC-id starting point as the two modes and by clarifying that distances are straight-line yards.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and result shape: entrances, NPCs, and vendors near a point, nearest first with distances in yards. It clearly scopes what is included and excluded, though it does not explicitly name sibling tools as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the two invocation modes: zone plus x/y, or an NPC id. It also gives exclusions for unreleased zones and game objects, but it does not direct the agent to an alternative sibling tool when this one is unsuitable.

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.