Skip to main content
Glama

Guild Wars 1 Build Compiler

by io.github.Graphmaxer

Decode a skill template code

decode_template
Read-onlyIdempotent

Decode an in-game GW1 skill template code (e.g. "OwpiMypMBg1cxcBAMBdmtIKAA") into professions, attribute allocations and the 8 skills with their stats and descriptions. Whitespace and line wraps in the pasted code are tolerated. This decodes a SINGLE build code; for a multi-hero paw-ned2 team blob, use decode_pawned_team instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe template code string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawYesThe raw decoded template (ids, not names)
skillsYesThe 8 bar slots in order
primaryYesPrimary profession name
secondaryYesSecondary profession name, null for none
attributesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / secondary / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / secondary / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / skills / items / properties / attribute / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / skills / items / properties / attribute / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / skills / items / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / skills / items / properties / name / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • addedOutput schema / properties / skills / items / properties / isRoleplay
      Added value: +{
+  "description": "PvE-only skill: max 3 per player bar, none on heroes",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / code / maxLength
      Added value: +128
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attributes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attribute": {
+            "type": "string"
+          },
+          "rank": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "attribute",
+          "rank"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "primary": {
+      "description": "Primary profession name",
+      "type": "string"
+    },
+    "raw": {
+      "description": "The raw decoded template (ids, not names)"
+    },
+    "secondary": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Secondary profession name, null for none"
+    },
+    "skills": {
+      "description": "The 8 bar slots in order",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "activation": {
+            "type": "number"
+          },
+          "adrenaline": {
+            "type": "number"
+          },
+          "attribute": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "description": {
+            "type": "string"
+          },
+          "elite": {
+            "type": "boolean"
+          },
+          "energy": {
+            "type": "number"
+          },
+          "name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "null for an empty bar slot"
+          },
+          "recharge": {
+            "type": "number"
+          },
+          "sacrifice": {
+            "type": "number"
+          },
+          "slot": {
+            "description": "Bar position 1-8",
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "slot",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "primary",
+    "secondary",
+    "attributes",
+    "skills",
+    "raw"
+  ],
+  "type": "object"
+}
  6. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description only needs to add behavioral context beyond that. It adds useful details: the decoded output contents and the single-code scope, and explicitly warns against passing multi-hero team blobs. This goes beyond the annotations without contradicting them.

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 sentences with zero filler: the first states purpose and outputs, the second adds input tolerance, and the third routes to the correct sibling tool. The most important scoping constraint is placed at the end but is clearly emphasized, and every sentence contributes to correct invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to enumerate return fields. It covers the input format, scope limitations, and output categories, and it references the correct alternative tool for the multi-hero case. This is complete for a single-parameter read-only decoding tool.

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?

The schema already documents the single 'code' parameter at 100% coverage with a basic description, so the baseline is 3. The tool description adds meaningful value by providing a concrete example, explaining that whitespace/line wraps are tolerated, and clarifying that the code must be a SINGLE build code rather than a multi-hero blob. This materially improves parameter understanding.

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 states a specific verb ('Decode'), a specific resource ('in-game GW1 skill template code'), and enumerates the exact outputs: professions, attribute allocations, and the 8 skills with stats and descriptions. It also distinguishes itself from the sibling tool decode_pawned_team by explicitly limiting scope to a SINGLE build code, so an agent can clearly tell which tool to pick.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: use for a single build code, and use decode_pawned_team for a multi-hero pawned-n2 team blob. It also provides a practical input-handling note that whitespace and line wraps are tolerated, which helps the agent pass user pasted code without pre-cleaning.

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

All Guild Wars 1 Build Compiler toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct operation: decoding team blobs vs. single templates vs. encoding; looking up a single hero vs. listing heroes; exact skill lookup vs. searching. Cross-references between similar tools (e.g., decode_pawned_team vs. decode_template) make boundaries clear.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: decode_*, encode_template, get_*, list_heroes, search_skills, validate_build. No mixed conventions or vague verbs.

Tool Count5/5

Eight tools is well-scoped for a build compiler: decoding/encoding, validation, and lookup utilities for skills and heroes. Each tool earns its place without redundancy or bloat.

Completeness4/5

The core lifecycle is covered: decode single/team, encode single template, validate, plus skill/hero discovery. A notable gap is the lack of a tool to encode a full team blob (paw-ned2 format), which would be the natural counterpart to decode_pawned_team, but agents can work around this by encoding individual templates.

Resources