Everloot: WoW Forever data

Auction history for one item

auction_history

Read-onlyIdempotent

Returns one item's dated auction history on one Forever realm: public full-scan days used by market_value, plus separate browsing sightings. Browsing prices are the median of each install's last scan that day. A day needs 3 reporters, or, while few players upload, Everloot's own installs; preserve the own-scan label and counts. Use the full realm name (CAMWOW US1 Realm 4 PvP); a unique whole-word suffix of at least two words also resolves. Ambiguous or unknown names return candidates; choose a full name before retrying. Full-scan days use the house with most units listed (ties: Alliance, Horde, Neutral), the same house as market_value structured content; browsing sightings remain a separate source, not split by house. No house selector exists; preserve the house named in the text. Use market_value for value and latest scan details, item_page for facts and vendor_page for vendor prices. Keep scan dates and corpus age; an old minimum is not a live auction offer. Missing data is unrecorded, not zero.

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": "auction_history"
  }
}

Input Schema

Name	Required	Description	Default
`realm`	Yes	The realm's full name as the game's realm list shows it, such as CAMWOW US1 Realm 4 PvP. A whole-word suffix of at least two words matching exactly one realm's full name (US1 Realm 4 PvP) is read as that realm; an unknown or ambiguous name answers with the realms to ask with.
`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.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / realm / description

Previous value: -"The realm's full name as the game's realm list shows it, such as CAMWOW US1 Realm 4 PvP. The end of exactly one realm's full name (US1 Realm 4 PvP) is read as that realm; an unknown or ambiguous name answers with the realms to ask with."New value: +"The realm's full name as the game's realm list shows it, such as CAMWOW US1 Realm 4 PvP. A whole-word suffix of at least two words matching exactly one realm's full name (US1 Realm 4 PvP) is read as that realm; an unknown or ambiguous name answers with the realms to ask with."

Changed6 schema fields changedNov 10, 2026

changedInput schema / properties / realm / description

Previous value: -"The realm's name, as the game shows it."New value: +"The realm's full name as the game's realm list shows it, such as CAMWOW US1 Realm 4 PvP. The end of exactly one realm's full name (US1 Realm 4 PvP) is read as that realm; an unknown or ambiguous name answers with the realms to ask with."

addedOutput schema / properties / page / properties / askedRealm

Added value: +{
+  "description": "The realm as asked, when it was read as an alias.",
+  "type": "string"
+}

addedOutput schema / properties / page / properties / candidates

Added value: +{
+  "description": "For ambiguous or unknown: the realms with public prices to ask with instead, closest first.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / page / properties / points / description

Previous value: -"Days 3 installs scanned the item on the realm, oldest first."New value: +"Single listings players saw while browsing: days 3 installs scanned the item on the realm, or one of Everloot's own installs did (reporters under 3), oldest first."

addedOutput schema / properties / page / properties / realmStatus

Added value: +{
+  "description": "exact: a realm Everloot holds scans for. alias: the end of exactly one public realm's full name, read as that realm (realm is its full name). ambiguous: the end of several realms' names, so nothing is read. unknown: no scan names that realm, so nothing is read; that is not an empty market.",
+  "enum": [
+    "exact",
+    "alias",
+    "ambiguous",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / page / properties / scanDays

Added value: +{
+  "description": "The public full-scan days market_value values the item by, the same days as its history, oldest first. Absent when the market is not connected.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "day": {
+        "type": "string"
+      },
+      "market": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "min": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "quantity": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "reporters": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "thin": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "day",
+      "min",
+      "market",
+      "quantity",
+      "reporters",
+      "thin"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes further in ways that matter for interpretation: the 3-reporter threshold (with an Everloot-install exception), median-of-last-scan aggregation, house selection with tie-breaking, and the warning that an old minimum 'is not a live auction offer'. It stops short of describing how many days the history spans or its ordering, which a history tool arguably should state.

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 purpose and the two data sources before any caveats, and most sentences carry real behavioral content. It is dense and slightly repetitive — the no-house-selector point is made twice ('Full-scan days use the house with most units listed' and 'No house selector exists; preserve the house named in the text') — but nothing is padded for its own sake.

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 two-parameter read tool with an output schema, the necessary burden is interpretive rather than structural, and the description covers ambiguity handling, aggregation semantics, house attribution, and the freshness caveat that prevents misreading stored scan minima as live listings. Return-field explanations are correctly omitted because an output schema exists.

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 the realm property description already spells out full-name resolution, two-word suffix matching, and candidate-return on ambiguity, so the description largely restates it. The only genuinely additive item is the workflow instruction to pick a full name before retrying; itemId adds nothing beyond the schema.

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?

Opens with a specific verb and resource ('Returns one item's dated auction history on one Forever realm') and immediately scopes the two data sources it merges: public full-scan days and browsing sightings. Too many overlapping siblings exist (market_value, item_page, vendor_page, population) for name alone to distinguish it, and the description handles that by naming the siblings it is not.

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?

Explicitly routes away from alternatives: 'Use market_value for value and latest scan details, item_page for facts and vendor_page for vendor prices.' It also prescribes realm-naming practice ('Use the full realm name... a unique whole-word suffix of at least two words also resolves') and a recovery path for ambiguity ('choose a full name before retrying').

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.

Auction history for one item

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources