Guild Wars 2

Currencies

currencies

Read-onlyIdempotent

Currencies.

Input Schema

Name	Required	Description	Default
`ids`	No
`lang`	No

Output Schema

Name	Required	Description	Default
`count`	Yes	Number of items returned.
`items`	Yes	List of Guild Wars 2 currencies

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "ids": "1,4,18"
+  },
+  {
+    "lang": "en"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of Guild Wars 2 currencies",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Currency description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Currency ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Currency name",
+            "type": "string"
+          },
+          "order": {
+            "description": "Display order",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, which provide a good safety profile. The description adds no behavioral context, but does not contradict annotations. Minimal value added beyond structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one word) but at the expense of necessary information. Conciseness should not sacrifice clarity; this is under-specification rather than efficient writing.

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

Completeness1/5

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

Given the tool has two undocumented parameters and an output schema, the description is wholly inadequate. It does not explain return values, filtering, or any usage context, leaving the agent blind.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the two parameters ('ids' and 'lang'). With no enum constraints and no parameter descriptions, the agent receives no guidance on valid values or their meaning.

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

Purpose1/5

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

The description is a tautology: 'Currencies.' It merely repeats the tool name without any verb or explanation of what the tool does, failing to convey the action or resource.

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

Usage Guidelines1/5

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

No usage guidance provided. The description does not indicate when to use this tool over siblings like 'commerce_prices' or 'commerce_listings', nor does it mention prerequisites or context.

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

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.