wow-api-mcp

Get Warcraft Wiki page

get_wiki_page

Fetch a World of Warcraft wiki page as markdown, useful for accessing API documentation, event handlers, and UI function references.

Instructions

Fetch a warcraft.wiki.gg page as markdown (cached ~24h). Useful pages: "TOC format", "World of Warcraft API", "Events", "Widget API", "API " for per-function pages, "UIHANDLER " for script handlers.

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

Input Schema

Name	Required	Description	Default
`title`	Yes	Page title, e.g. "TOC format" or "API C_Timer.After"
`maxChars`	No	Truncate output beyond this length

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Without annotations, description adds caching behavior ('cached ~24h') and that output is markdown. However, it does not disclose error handling (e.g., page not found), rate limits, or authentication needs. Cache detail is helpful but incomplete for full transparency.

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?

Two sentences: first sentence states purpose and behavior, second provides examples. No unnecessary words, front-loaded with key information.

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?

Given no output schema, the description covers purpose, cache behavior, and example inputs. Lacks details on error handling or output format beyond markdown, but sufficient for a simple fetch tool with two parameters.

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 covers both parameters with descriptions (100% coverage). Description adds value by listing example valid titles ('TOC format', 'API C_Timer.After'), which helps the agent understand the title parameter beyond its schema description. No additional semantics for maxChars.

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?

Clearly states the tool fetches a Warcraft wiki page as markdown, with specific verb 'Fetch' and resource 'page as markdown'. Provides concrete examples of useful pages, distinguishing it from sibling tools like search_wiki which is for searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit examples of when to use ('Useful pages: ...'), implying the tool is for fetching known page titles. Does not explicitly mention when not to use or alternative tools, but examples guide usage effectively.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server