Skip to main content
Glama
Sign In

Guild Wars 2

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Items

items
Read-onlyIdempotent

Fetch Guild Wars 2 item details by comma-separated IDs or by page; returns item name, type, rarity, level, vendor value, icon, and game flags.

Input Schema

NameRequiredDescriptionDefault
idsNo
langNo
pageNo
page_sizeNo

Output Schema

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

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": "Item description",
-    "type": "string"
-  },
-  "id": {
-    "description": "Item ID",
-    "type": "number"
-  },
-  "level": {
-    "description": "Required level",
-    "type": "number"
-  },
-  "name": {
-    "description": "Item name",
-    "type": "string"
-  },
-  "rarity": {
-    "description": "Item rarity",
-    "type": "string"
-  },
-  "type": {
-    "description": "Item type",
-    "type": "string"
-  },
-  "vendor_value": {
-    "description": "Vendor value in coins",
-    "type": "number"
-  }
-}
    • 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": 200
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of Guild Wars 2 items",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Item description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Item ID",
+            "type": "number"
+          },
+          "level": {
+            "description": "Required level",
+            "type": "number"
+          },
+          "name": {
+            "description": "Item name",
+            "type": "string"
+          },
+          "rarity": {
+            "description": "Item rarity",
+            "type": "string"
+          },
+          "type": {
+            "description": "Item type",
+            "type": "string"
+          },
+          "vendor_value": {
+            "description": "Vendor value in coins",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the agent knows it's a safe read operation. The description adds context by listing returned fields (name, type, rarity, etc.), which is useful but does not disclose additional behaviors like rate limits or pagination defaults.

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, well-structured sentence with a clear verb and resource. It is front-loaded and avoids unnecessary words, though it could be slightly improved by separating the two modes for readability.

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

Completeness3/5

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

The description lists returned fields, which is helpful given the output schema exists. However, it omits details like default page size, language usage, or error handling. For a tool with 4 optional parameters and no parameter descriptions, more context is needed.

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?

With 0% schema description coverage, the description must compensate. It mentions comma-separated IDs and page modes, but does not explicitly map to the 'ids', 'page', 'page_size', or 'lang' parameters. It does not clarify the format or constraints for these parameters, leaving significant gaps.

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 states the verb 'Fetch', the resource 'Guild Wars 2 item details', and specifies two distinct modes (by comma-separated IDs or by page). It also lists the returned fields, making it easy to differentiate from sibling tools like 'achievements' or 'currencies'.

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 two usage patterns (by IDs or by page) but does not provide explicit guidance on when to choose one over the other, nor does it mention when not to use this tool. No alternatives are cited.

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