Everloot: WoW Forever data

Item categories: class, subclass, slot and quality

item_categories

Read-onlyIdempotent

Lists item categories from the game files (found in game files, unconfirmed, with the build): class and subclass with the client's English names and slugs, slot and quality. With no arguments, the whole tree with item counts. With item, that item's category path. With class (a slug such as weapon or armor), and optionally subclass, slot and quality slugs, the item ids in it. Use it to place an item in its category or to list a category; use item_page for an item's name and stats, and entity_relations for where it comes from. Ids only: item names come from player uploads, through item_page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "item_categories"
  }
}

Input Schema

Name	Required	Description
`item`	No	An item id: answers its class, subclass, slot and quality.
`slot`	No	Slot slug, such as head, chest, one-hand or trinket.
`class`	No	Class slug, such as weapon, armor, consumable or trade-goods.
`limit`	No	Most items listed, 1 to 100, default 25.
`quality`	No	poor, common, uncommon, rare, epic, legendary, artifact or heirloom.
`subclass`	No	Subclass slug or number within the class, such as one-handed-swords or cloth.

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.
`item`	No	With item: its path, or null when the item is not in the build.
`build`	Yes
`error`	No	A class or subclass that is not in the build.
`items`	No	With class: the items in the category, up to limit.
`label`	Yes
`total`	No	With class: how many items match, listed or not.
`credit`	Yes
`classes`	No	With no arguments: the whole tree, classes with items only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / limit / description

Previous value: -"Most items listed."New value: +"Most items listed, 1 to 100, default 25."

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

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuine context not in the annotations: data is derived from game files and is 'unconfirmed, with the build,' and results are ids only because names come from player uploads. It does not note the default/limit behavior when a class query returns many ids, which the schema covers but the description could have surfaced.

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?

The mode descriptions and sibling routing are front-loaded and every clause carries information. Minor friction from the parenthetical 'found in game files, unconfirmed, with the build,' which reads awkwardly and slightly duplicates the opening phrase.

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 shapes need not be spelled out. The description covers all three call patterns, the id-only limitation, the data provenance caveat, and the two sibling alternatives — sufficient for an agent to invoke it correctly on the first try.

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 baseline is 3; the description earns above it by explaining the conditional semantics the schema cannot express — no arguments yields the whole tree with counts, `item` yields that item's category path, and `class` with optional subclass/slot/quality yields item ids. Only `limit` is left unexplained, and the schema handles it.

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 ('Lists item categories from the game files') and immediately enumerates the dimensions covered: class, subclass, slot and quality. It clearly separates itself from item_page (names and stats) and entity_relations (provenance), so an agent can discriminate without opening a 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?

Explicit routing is present: 'Use it to place an item in its category or to list a category; use item_page for an item's name and stats, and entity_relations for where it comes from.' The three invocation modes (no args, item, class+optional filters) tell the agent exactly which call shape maps to which question.

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.