Everloot: WoW Forever data

Get records by exact name

get_by_name

Read-onlyIdempotent

Returns the records whose full name matches exactly, case-insensitively, optionally narrowed to one record kind. Use it to disambiguate when you know the exact name and want the id without a ranked search; use search_knowledge for partial names, keywords or questions. Several records can share a name across kinds, so check each hit's kind. Empty hits mean no record has that exact name.

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": {
      "name": "<name>"
    },
    "name": "get_by_name"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	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.
`name`	Yes	The full record name, any case, up to 200 characters.

Output Schema

Name	Required	Description	Default
`hits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

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

changedInput schema / properties / name / description

Previous value: -"Full record name."New value: +"The full record name, any case, up to 200 characters."

Changed4 schema fields changedNov 4, 2026

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

Changed1 schema field changedOct 20, 2026

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"
+}

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: matching is case-insensitive, matches are exact-full-name only, multiple records can share a name across kinds, and empty hits are a definitive negative rather than an error. It does not mention result caps or ordering, which is the remaining gap.

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 core behavior and the case-insensitive exactness are front-loaded, followed by usage routing, then the collision caveat and the empty-result meaning. Every clause carries distinct information with no repetition of the schema.

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-shape explanation is unnecessary, and the description instead covers the interpretive edges an agent actually needs: cross-kind duplicates and empty results. For a two-parameter lookup with full schema coverage, nothing material 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% and the enum description already explains each kind's provenance, so the baseline is 3. The description goes slightly beyond the schema by explaining why the kind parameter matters (names collide across kinds, so check each hit's kind) and by reinforcing case-insensitive matching semantics for name.

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 description gives a specific verb and resource ("returns the records whose full name matches exactly, case-insensitively") and immediately bounds the scope with the optional kind narrowing. It also names the sibling it is not (search_knowledge), so an agent can distinguish it 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?

It states the selecting condition explicitly ("use it to disambiguate when you know the exact name and want the id without a ranked search") and routes the alternative cases to a named sibling (partial names, keywords, questions -> search_knowledge). Both the when and the when-not are covered.

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.