Skip to main content
Glama
Sign In

Everloot: WoW Forever data

by app.everloot
OverviewDiscussionsAdmin

Search the Everloot knowledge base

search_knowledge
Read-onlyIdempotent

Searches WoW lore, Forever reference data and the game-file catalogs (achievements, factions, titles, quest chains, mounts, legacy perks, races, instances) by names, keywords or a question. Exact-name matches rank first. Every hit carries its id, kind, source, licence and date, and a game-file hit says when player uploads confirm it. Use it to find a record from a name or a topic, then pass the hit's id to get_entity for its summary, or to fetch as a string for the whole text. Use get_by_name when you already know the exact full name, and answer_sources when you need cited evidence for a question rather than records. search is the same search in the ChatGPT connector shape.

Input Schema

NameRequiredDescriptionDefault
kindNoNarrow to one record kind. achievement, faction, title, quest_chain, mount, legacy_perk, race and instance come from the game files (found in game files, unconfirmed); item, npc, object, quest, zone, spell, lore_page, creator and realm from the knowledge release; build is an Everloot team starter talent build, not observed. Without it, every kind.
limitNoMost hits, 1 to 25, default 8.
queryYesWhat to look up: names, questions, keywords. Question words are ignored.
versionNoNarrow to one game version: forever, classic, retail or lore. Without it, every version.

Output Schema

NameRequiredDescriptionDefault
hitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Narrow to one record kind."New value: +"Narrow to one record kind. achievement, faction, title, quest_chain, mount, legacy_perk, race and instance come from the game files (found in game files, unconfirmed); item, npc, object, quest, zone, spell, lore_page, creator and realm from the knowledge release; build is an Everloot team starter talent build, not observed. Without it, every kind."
    • addedInput schema / properties / limit / description
      Added value: +"Most hits, 1 to 25, default 8."
    • changedInput schema / properties / version / description
      Previous value: -"Narrow to one game version."New value: +"Narrow to one game version: forever, classic, retail or lore. Without it, every version."
  2. Changed4 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "item",
-  "npc",
-  "object",
-  "quest",
-  "zone",
-  "spell",
-  "lore_page",
-  "creator",
-  "realm"
-]New value: +[
+  "item",
+  "npc",
+  "object",
+  "quest",
+  "zone",
+  "spell",
+  "lore_page",
+  "creator",
+  "realm",
+  "achievement",
+  "faction",
+  "title",
+  "quest_chain",
+  "mount",
+  "legacy_perk",
+  "race",
+  "instance",
+  "build"
+]
    • addedOutput schema / properties / hits / items / properties / confirmed
      Added value: +{
+  "additionalProperties": false,
+  "description": "Present when player uploads confirm this game-file entry (3 or more installs agree). asOf is the date the rollup was current.",
+  "properties": {
+    "asOf": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "asOf"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / hits / items / properties / kind / enum
      Previous value: -[
-  "item",
-  "npc",
-  "object",
-  "quest",
-  "zone",
-  "spell",
-  "lore_page",
-  "creator",
-  "realm"
-]New value: +[
+  "item",
+  "npc",
+  "object",
+  "quest",
+  "zone",
+  "spell",
+  "lore_page",
+  "creator",
+  "realm",
+  "achievement",
+  "faction",
+  "title",
+  "quest_chain",
+  "mount",
+  "legacy_perk",
+  "race",
+  "instance",
+  "build"
+]
    • changedOutput schema / properties / hits / items / properties / url / description
      Previous value: -"The record's page on everloot.app, absolute: an indexed lore page. Absent for a record the site has no page for."New value: +"The record's page on everloot.app, absolute: an indexed lore page or a catalog page. Absent for a record the site has no page for."
  3. Changed1 schema field changed
    • addedOutput schema / properties / hits / items / properties / url
      Added value: +{
+  "description": "The record's page on everloot.app, absolute: an indexed lore page. Absent for a record the site has no page for.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: exact-name matches rank first, every hit carries id/kind/source/licence/date, and game-file hits flag whether player uploads confirm them. It stops short of describing pagination or how to page past `limit`, which keeps it off a 5.

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 scope, then the ranking rule, then the chaining/alternative guidance — a sensible priority order with no filler sentences. The closing remark about 'search' being the same search in the ChatGPT connector shape is useful but slightly awkwardly appended.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter search with an output schema, the description covers scope, ranking, result metadata, the id-to-get_entity follow-up and all relevant sibling alternatives. The only soft spot is the phrase 'or to fetch as a string for the whole text', which names the sibling but leaves the fetch mechanics to that tool's own definition.

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 description coverage is 100%, so the enum groupings for `kind`, the version values and the limit bounds are already fully documented in the schema. The description restates that searching happens by 'names, keywords or a question' and that question words are ignored, but adds no syntax or formatting guidance beyond it. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Searches WoW lore, Forever reference data and the game-file catalogs...') and enumerates the covered record families. It explicitly separates itself from get_by_name, answer_sources, get_entity and the connector-shaped 'search' sibling, so an agent can route without opening schemas.

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 workflow ('find a record from a name or a topic, then pass the hit's id to get_entity') plus two named alternatives with their selecting conditions: get_by_name for known exact full names, answer_sources when cited evidence is wanted instead of records. Exclusions are stated, not implied.

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 toolsInspect
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.

Resources