Skip to main content
Glama
Sign In

Guild Wars 2

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Achievements

achievements
Read-onlyIdempotent

Fetch Guild Wars 2 achievement details by comma-separated IDs or by page; returns achievement name, description, category, tiers, point rewards, and prerequisites.

Input Schema

NameRequiredDescriptionDefault
idsNo
langNo
pageNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
countNoNumber of items returned.
itemsNoList of Guild Wars 2 achievements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / count / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / items / items / properties
      Removed value: -{
-  "description": {
-    "description": "Achievement description",
-    "type": "string"
-  },
-  "id": {
-    "description": "Achievement ID",
-    "type": "number"
-  },
-  "locked_text": {
-    "description": "Locked achievement text",
-    "type": "string"
-  },
-  "name": {
-    "description": "Achievement name",
-    "type": "string"
-  },
-  "points": {
-    "description": "Achievement points",
-    "type": "number"
-  },
-  "requirement": {
-    "description": "Achievement requirement",
-    "type": "string"
-  }
-}
    • changedOutput schema / properties / items / items / type
      Previous value: -"object"New value: +"number"
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ids": "1,2,3"
+  },
+  {
+    "lang": "en",
+    "page": 1,
+    "page_size": 100
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of Guild Wars 2 achievements",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Achievement description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Achievement ID",
+            "type": "number"
+          },
+          "locked_text": {
+            "description": "Locked achievement text",
+            "type": "string"
+          },
+          "name": {
+            "description": "Achievement name",
+            "type": "string"
+          },
+          "points": {
+            "description": "Achievement points",
+            "type": "number"
+          },
+          "requirement": {
+            "description": "Achievement requirement",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive, which covers key behavioral traits. The description adds value by listing the specific fields returned (name, description, category, tiers, points, prerequisites), providing more detail than the annotations alone. No contradictions are present.

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, front-loaded sentence that efficiently conveys the tool's purpose and return fields. It wastes no words, though a slight restructuring (e.g., separating modes) could improve readability but is not necessary.

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?

Given the tool's simplicity (4 optional parameters, no enums, output schema exists), the description covers the main usage modes and return values. Minor gaps remain for 'lang' and 'page_size' semantics, but overall it is sufficiently complete for an agent to use the tool correctly.

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 input schema has 0% description coverage, so the description must compensate. It explains that 'ids' takes comma-separated IDs and that 'page' is for pagination, but it does not clarify the purpose of 'lang' or 'page_size'. This leaves two parameters undocumented in both schema and description, resulting in a partial explanation only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the action ('Fetch') and resource ('Guild Wars 2 achievement details'), and outlines two modes of operation (by IDs or by page). However, it does not explicitly distinguish this tool from sibling tools that also retrieve game data (e.g., items, currencies), which prevents a score of 5.

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 the tool (to fetch achievements by either IDs or page), but it provides no explicit guidance on when to choose one mode over the other, nor does it mention alternatives or situations where this tool should not be used. This is adequate but lacks clear direction for selection among sibling tools.

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

All Guild Wars 2 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources