Guild Wars 1 MCP

Analyze GW1 template code

gw1_template_code_analyze

Validate and decode Guild Wars template codes, extracting primary/secondary professions, attributes, and skill names from the Guild Wars Wiki index.

Instructions

Validate, classify, and decode a Guild Wars template/build code. Skill templates are fully decoded into primary/secondary professions, attributes with points, and the eight skills resolved to names via the bundled Guild Wars Wiki skill index.

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": {
      "input": "<input>"
    },
    "name": "gw1_template_code_analyze"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden. It discloses the decode behavior (professions, attributes, skills via bundled index) but omits details on invalid input handling, authentication, rate limits, or side effects. It states the action truthfully but could be more comprehensive.

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 description is a single sentence that efficiently conveys the tool's purpose and decoding details. It is front-loaded with the main verbs. No wasted words, though it could be broken into smaller sentences for readability.

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?

Despite lacking an output schema and annotations, the description gives a good overview of the input (template code) and output (professions, attributes, skills). It does not explain error behavior or output format, but for a single-input tool, the main use case is adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema defines one input parameter with length constraints. The description calls it 'template/build code', which adds slight context beyond 'string', but does not explain expected format, examples, or encoding differences. With 0% schema coverage in descriptions, the value added over the schema is minimal.

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?

The description clearly specifies three main actions (validate, classify, decode) on a specific resource (GW1 template/build code). It lists the decoding outputs (professions, attributes, skills), making it distinct from sibling tools like gw1_template_encode or search tools.

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?

The description implies when to use (when given a template code to analyze) but lacks explicit guidance on when not to use or explicit comparison to alternatives. For a tool with many siblings, stating that encoding is a separate tool would improve clarity, but it's not required.

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

Deploy Server