Everloot: WoW Forever data

Forever market value for one item

market_value

Read-onlyIdempotent

Returns the market value, minimum buyout, historical value and units listed for one item on one WoW: Forever realm, from full auction scans players started and uploaded. A day is public after 3 reporters (distinct upload addresses) scanned the item, and its value is the median of theirs. Market value is a weighted mean of the public days up to 14 calendar days old, newer days weighing more, leaving out thin days (5 units listed or fewer) and outlier days. Historical is the median of the public days in the last 60 calendar days, of the days that are not thin when there are any. Use it for what an item is worth now; use auction_history for the price over time, and vendor_page for vendor prices. 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": {
      "realm": "<realm>",
      "itemId": "<itemId>"
    },
    "name": "market_value"
  }
}

Input Schema

Name	Required	Description	Default
`realm`	Yes	The realm's name, as the game shows it.
`itemId`	Yes	The game's item id, as item_page takes it.

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 / itemId / description

Previous value: -"Item id."New value: +"The game's item id, as item_page takes it."

changedInput schema / properties / realm / description

Previous value: -"Realm name."New value: +"The realm's name, as the game shows it."

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 declare a safe read-only, idempotent operation, but the description earns credit for adding provenance ('full auction scans players started and uploaded'), a data-eligibility threshold (3 distinct reporter addresses), the aggregation method (median of reporters, weighted mean over 14 days, thin-day and outlier exclusion), a 60-day historical window, an auth/connection note ('Reads Everloot's public player data when connected'), and an explicit missing-data contract.

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 what is returned, then the methodology, then the sibling routing; every sentence carries information. The middle methodological sentences are dense and long, which costs a point on immediate scannability, but none of the content is filler given how non-obvious the aggregation rules are.

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-value shape need not be explained, and the description still covers data provenance, eligibility thresholds, aggregation rules, the time window, the connected-data dependency, and a failure contract. Nothing an agent needs in order to call this correctly or interpret its output 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% and both parameters are fully described in the schema (realm as the game-shown name, itemId as item_page takes it), so the schema already carries the burden. The description only reinforces the 'one realm, one item' cardinality, which is a marginal addition over structured data — 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?

The opening sentence names a specific verb (Returns) and enumerates the exact returned quantities — market value, minimum buyout, historical value, units listed — scoped to 'one item on one WoW: Forever realm'. This is unmistakable against siblings like auction_history or vendor_page, which are named 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?

It gives an explicit routing rule: 'use it for what an item is worth now; use auction_history for the price over time, and vendor_page for vendor prices.' Both alternatives and the condition that selects them are stated, so no inference is required from the agent.

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.