Guild Wars 1 Build Compiler

Get a Guild Wars 1 skill

get_skill

Read-onlyIdempotent

Look up a single GW1 skill by exact English name or by template skill id. Returns full stats (energy, activation, recharge, adrenaline, sacrifice), profession, attribute, campaign, elite flag and description. If the name is not found, returns the closest matches so you can correct spelling. Use this when you already know the exact skill; to discover skills by profession, attribute or name fragment, use search_skills instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Template skill id
`name`	No	Exact skill name, e.g. "Mystic Regeneration". The official French name also resolves ("Sceau de guérison" -> Healing Signet); every other name field on every other tool is English-only.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`type`	Yes	Skill type, e.g. Enchantment Spell
`elite`	Yes
`energy`	Yes
`upkeep`	Yes
`campaign`	Yes
`overcast`	Yes
`recharge`	Yes
`attribute`	Yes
`sacrifice`	Yes
`activation`	Yes
`adrenaline`	Yes
`isRoleplay`	Yes	PvE-only skill: max 3 per player bar, none on heroes
`profession`	Yes
`description`	Yes
`isPvpVersion`	Yes

Schema Changelog

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

Changed9 schema fields changedAug 31, 2026

changedInput schema / properties / name / description

Previous value: -"Exact English skill name, e.g. \"Mystic Regeneration\""New value: +"Exact skill name, e.g. \"Mystic Regeneration\". The official French name also resolves (\"Sceau de guérison\" -> Healing Signet); every other name field on every other tool is English-only."

removedOutput schema / properties / attribute / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / attribute / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / campaign / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / campaign / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / profession / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / profession / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedAug 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedJul 21, 2026

addedOutput schema / properties / isRoleplay

Added value: +{
+  "description": "PvE-only skill: max 3 per player bar, none on heroes",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "elite",
-  "energy",
-  "activation",
-  "recharge",
-  "adrenaline",
-  "sacrifice",
-  "overcast",
-  "upkeep",
-  "description",
-  "isPvpVersion",
-  "profession",
-  "attribute",
-  "campaign",
-  "type"
-]New value: +[
+  "id",
+  "name",
+  "elite",
+  "isRoleplay",
+  "energy",
+  "activation",
+  "recharge",
+  "adrenaline",
+  "sacrifice",
+  "overcast",
+  "upkeep",
+  "description",
+  "isPvpVersion",
+  "profession",
+  "attribute",
+  "campaign",
+  "type"
+]

Changed1 schema field changedJul 21, 2026
- addedInput schema / properties / name / maxLength
```
Added value: +64
```

Changed1 schema field changedJul 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "activation": {
+      "type": "number"
+    },
+    "adrenaline": {
+      "type": "number"
+    },
+    "attribute": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "campaign": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": {
+      "type": "string"
+    },
+    "elite": {
+      "type": "boolean"
+    },
+    "energy": {
+      "type": "number"
+    },
+    "id": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "isPvpVersion": {
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "overcast": {
+      "type": "number"
+    },
+    "profession": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "recharge": {
+      "type": "number"
+    },
+    "sacrifice": {
+      "type": "number"
+    },
+    "type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Skill type, e.g. Enchantment Spell"
+    },
+    "upkeep": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "elite",
+    "energy",
+    "activation",
+    "recharge",
+    "adrenaline",
+    "sacrifice",
+    "overcast",
+    "upkeep",
+    "description",
+    "isPvpVersion",
+    "profession",
+    "attribute",
+    "campaign",
+    "type"
+  ],
+  "type": "object"
+}

First observedJul 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar for additional disclosure is lower. The description adds meaningful behavior: it returns full stats and, on no exact match, returns closest matching names. This clarifies failure behavior beyond what the annotations express.

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?

The description is compact, logically ordered, and front-loaded with the core action before the return-value and fallback details. Every sentence earns its place, and the sibling-tool pointer is included without bloat.

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?

For a simple read-only lookup tool, the description plus schema and annotations cover purpose, parameter semantics, return contents, failure behavior, and the alternative tool. There is no material gap an agent would need to fill by trial and error.

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?

The input schema already documents both parameters thoroughly with 100% coverage, so the baseline is 3. The description reinforces the id/name lookup modes but does not add substantial semantic detail beyond the schema, nor does it clarify precedence if both are supplied. It is adequate, not rich.

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 says exactly what the tool does: look up a single GW1 skill by exact English name or template skill id. It lists the fields returned and explicitly contrasts itself with search_skills, making its scope and differences from siblings clear.

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 guidance: use this tool when you already know the exact skill, and use search_skills when discovering skills by profession, attribute, or name fragment. It also explains the nearest-match fallback for misspellings, which helps an agent decide whether this tool will still be useful.

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 tools Inspect

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.

Get a Guild Wars 1 skill

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources