Skip to main content
Glama

Guild Wars 2

by io.github.pipeworx-io

Commerce Prices

commerce_prices
Read-onlyIdempotent

Bulk Guild Wars 2 Trading Post buy/sell quotes for many numeric item IDs at once; returns the raw copper unit_price and open quantity on each side for every ID passed. Use guild_wars_2_item_price for a single item looked up by its name with gold/silver/copper formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated numeric item IDs, e.g. "19976,19721".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of items returned.
itemsNoTrading post prices

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / properties / ids / description
      Added value: +"Comma-separated numeric item IDs, e.g. \"19976,19721\"."
  2. Changed4 schema fields changed
    • changedOutput schema / properties / count / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / items / items / properties
      Removed value: -{
-  "buys": {
-    "properties": {
-      "quantity": {
-        "description": "Buy quantity",
-        "type": "number"
-      },
-      "unit_price": {
-        "description": "Buy unit price",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "id": {
-    "description": "Item ID",
-    "type": "number"
-  },
-  "sells": {
-    "properties": {
-      "quantity": {
-        "description": "Sell quantity",
-        "type": "number"
-      },
-      "unit_price": {
-        "description": "Sell unit price",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "whitelisted": {
-    "description": "Whether item is whitelisted",
-    "type": "boolean"
-  }
-}
    • changedOutput schema / properties / items / items / type
      Previous value: -"object"New value: +"number"
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ids": "19684,24291"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "Trading post prices",
+      "items": {
+        "properties": {
+          "buys": {
+            "properties": {
+              "quantity": {
+                "description": "Buy quantity",
+                "type": "number"
+              },
+              "unit_price": {
+                "description": "Buy unit price",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Item ID",
+            "type": "number"
+          },
+          "sells": {
+            "properties": {
+              "quantity": {
+                "description": "Sell quantity",
+                "type": "number"
+              },
+              "unit_price": {
+                "description": "Sell unit price",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "whitelisted": {
+            "description": "Whether item is whitelisted",
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior, but the description adds valuable context by specifying the raw output format (copper unit_price, open quantity per side) and the numeric-ID requirement. This goes beyond the annotations, though it doesn't discuss error handling or rate limits.

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 two sentences: the first establishes purpose and output, the second provides an alternative. It is front-loaded, economical, and contains no redundant or filler text.

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 output schema exists and annotations cover safety, the description fully covers purpose, usage, and output format for a simple one-parameter tool. No significant gaps remain.

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?

Schema coverage is 100%: the ids parameter is described as 'Comma-separated numeric item IDs.' The description only reinforces 'many numeric item IDs,' adding no new semantic detail beyond what the schema already provides, so baseline 3 is appropriate.

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 opens with a specific action: 'Bulk Guild Wars 2 Trading Post buy/sell quotes for many numeric item IDs at once.' It clearly names the resource (Trading Post quotes) and distinguishes itself from guild_wars_2_item_price, which handles single items by name with formatted prices.

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?

Explicit guidance is given: 'Use guild_wars_2_item_price for a single item looked up by its name with gold/silver/copper formatting.' This tells the agent when to use this bulk tool vs the named alternative, making the choice straightforward.

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

C2.8/5.0
Disambiguation2/5

The set mixes two unrelated domains (Guild Wars 2 endpoints and a broad Pipeworx data-research suite), and within each there are near-duplicates: ask_pipeworx vs ask_pipeworx_beta are functionally identical, commerce_prices vs guild_wars_2_item_price vs commerce_listings overlap on Trading Post data, and ask_pipeworx/ask_pipeworx_grounded/deep_research all route questions to the same source catalog. An agent could easily select the wrong tool.

Naming Consistency3/5

Names are all snake_case and readable, but there is no consistent pattern: some are bare nouns (achievements, currencies, quaggans, worlds, build), some are verb_noun (resolve_entity, validate_claim, generate_llms_txt), some are ask_* (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded), and some are compound names (polymarket_kalshi_spread, guild_wars_2_item_price). Minor deviations would be fine, but this is a genuine mix of conventions.

Tool Count2/5

42 tools is far beyond the well-scoped range, and the majority are unrelated to the 'Guild Wars 2' server name (only ~11 tools are GW2 API endpoints; the rest are Pipeworx data-research/meta tools). This feels like two or three servers merged into one.

Completeness2/5

For a Guild Wars 2 server, the coverage is thin: it has items, prices, achievements, worlds, and WvW, but no recipes, guilds, characters, skills, maps, or PvE content. For the broader data-research domain implied by most tools, the surface is sprawling but still lacks depth in several areas. The result is a set that is neither complete for GW2 nor coherently scoped for anything else.

Resources