https://therealbill.github.io/gw2-mcp/explanation/Recent content in Explanation on GW2 MCP ServerHugoen-ushttps://therealbill.github.io/gw2-mcp/explanation/design-decisions/Mon, 01 Jan 0001 00:00:00 +0000https://therealbill.github.io/gw2-mcp/explanation/design-decisions/<p>This page explains the major design decisions in the GW2 MCP Server and the reasoning behind them. Understanding these decisions will help you make sense of the codebase&rsquo;s structure and anticipate how changes in one area affect others.</p> <p>For the structural overview of the system itself, see <a href="https://therealbill.github.io/gw2-mcp/explanation/architecture/">Architecture</a> .</p> <h2 id="jsonrawmessage-for-variable-structures">json.RawMessage for variable structures<a class="anchor" href="#jsonrawmessage-for-variable-structures">#</a></h2> <h3 id="the-problem">The problem<a class="anchor" href="#the-problem">#</a></h3> <p>The Guild Wars 2 API returns deeply nested, polymorphic JSON. The <code>/v2/items</code> endpoint alone has over 20 item subtypes &ndash; Weapon, Armor, Consumable, Trinket, UpgradeComponent, and many more &ndash; each with a different <code>details</code> object. A Weapon&rsquo;s details include <code>damage_type</code>, <code>min_power</code>, and <code>max_power</code>; an Armor&rsquo;s details include <code>weight_class</code> and <code>defense</code>. Character data is similarly variable: equipment, skills, specializations, build tabs, and equipment tabs all carry deeply nested structures that differ by profession and game mode.</p>https://therealbill.github.io/gw2-mcp/explanation/architecture/Mon, 01 Jan 0001 00:00:00 +0000https://therealbill.github.io/gw2-mcp/explanation/architecture/How the GW2 MCP Server is structured and why