Resources and prompts
The documents and ready-made prompts the server offers beside its tools.
Resources#
Documents an assistant reads whole, with resources/read, instead of calling a tool with arguments. Their shapes are in /schema/mcp/resources.json.
| URI | What it holds |
|---|---|
everloot://builds | The build the game-file facts come from, and every build Blizzard's version service has listed, with when Everloot first saw it. JSON. |
everloot://methodology | How uploads become facts: three installs must agree, unrecorded is never zero, game files and play are kept apart, and what is never published. Markdown. |
everloot://data-policy | The data policy in short: what is published, what is refused, the licence and credit line, and the limits on bulk copying. Markdown. |
Entity resources#
Entity pages read as resources too, one URI per entity. Each answers with the same JSON as the named tool's structured answer, so a client that prefers resources to tool calls gets the same page. The tools are on the overview; one example is item_page.
| URI template | What it holds |
|---|---|
everloot://item/{id} | The item_page answer for an item id: agreed name, drop rates with loot-window counts, map pins. The same JSON as item_page's structured answer. |
everloot://npc/{id} | The npc_page answer for an NPC id: agreed name and map pins. The same JSON as npc_page's structured answer. |
everloot://quest/{id} | The quest_page answer for a quest id: title, level, giver, turn-in and rewards. The same JSON as quest_page's structured answer. |
everloot://vendor/{id} | The vendor_page answer for a vendor NPC id: what it sells, with copper prices. The same JSON as vendor_page's structured answer. |
everloot://object/{id} | The object_page answer for an object's entry id: what players looted from it. The same JSON as object_page's structured answer. |
everloot://talents/{class} | The talent_tree answer for a class slug: every node with its talents, ranks, position, prerequisites and gate. The same JSON as talent_tree's structured answer. |
Prompts#
Ready-made instructions a client offers as commands (prompts/get). You fill the argument, and the assistant gets a message that says which tools to call and how to treat what they return. Their arguments are in /schema/mcp/prompts.json.
| Prompt | What it does |
|---|---|
answer_with_sources | Answer a question from answer_sources, citing every piece with its source, licence and date. Takes the question. |
review_talent_plan | Read a share code with talent_plan and the trees with talent_tree, then describe the build and every problem. Takes the code or a calculator link. |
what_changed | Summarize recent_changes newest first, with links and only the excerpts the tool gives. Takes forever or classic, or nothing for both. |