blizzard-wow-mcp

wow_token_tracker

Track WoW Token prices across US, EU, KR, and TW. Analyze historical trends and get buy/sell timing recommendations for real-money economy intelligence.

Instructions

Track WoW Token prices across all regions. Historical data, trend analysis, and optimal buy/sell timing recommendations. Real-money economy intelligence.

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": "wow_token_tracker"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Region to track	all
`history_days`	No	Days of history
`include_forecast`	No	Include price forecast

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 13, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses it provides 'optimal buy/sell timing recommendations' and 'real-money economy intelligence', indicating read-only analysis. However, lacks explicit statement about non-destructive behavior or permissions needed.

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?

Three concise sentences, no fluff. Front-loaded with core purpose, then details. Every sentence adds value.

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?

Moderate complexity (3 params, no nested objects). No output schema, but description mentions historical data, trend analysis, and recommendations, providing adequate expectations. Could detail return format, but still sufficient.

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 coverage is 100% with descriptions for all three parameters. Description adds no extra parameter details beyond schema. Baseline 3 is appropriate as schema already documents region, history_days, and include_forecast.

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?

Description clearly states the tool tracks WoW Token prices across all regions, with historical data and trend analysis. This distinguishes it from siblings like wow_price_history (general items) and wow_market_snapshot (snapshot). Specific verb 'Track' and resource 'WoW Token prices'.

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

Usage Guidelines3/5

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

Description implies usage for WoW Token economy intelligence but does not explicitly state when to use vs alternatives like wow_price_history or wow_market_snapshot. No exclusions or when-not-to-use guidance.

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

Deploy Server