Skip to main content
Glama
Sign In

Guild Wars 2

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Worlds

worlds
Read-onlyIdempotent

Fetch Guild Wars 2 world (server) details by comma-separated IDs, or return the full index of world IDs; includes world name and population level.

Input Schema

NameRequiredDescriptionDefault
idsNoComma-sep ids; omit for index.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "ids": "1,2,3"
-  },
-  {}
-]New value: +[
+  {
+    "ids": "1013,1019,1022"
+  },
+  {}
+]
  2. Changed4 schema fields changed
    • changedOutput schema / properties / count / type
      Previous value: -"integer"New value: +"number"
    • removedOutput schema / properties / items / items / properties
      Removed value: -{
-  "id": {
-    "description": "World ID",
-    "type": "number"
-  },
-  "name": {
-    "description": "World name",
-    "type": "string"
-  }
-}
    • 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": "1,2,3"
+  },
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "description": "List of Guild Wars 2 worlds",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "World ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "World name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds behavioral context beyond annotations by explaining two invocation modes (by IDs vs. full index) and the return fields (name, population level), which helps the agent understand what to expect.

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 a single sentence that front-loads the verb and resource, clearly covers both usage modes, and mentions key output fields. There is no wasted wording, making it highly concise and well-structured.

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 tool with one optional parameter, an output schema, and strong annotations, the description is complete. It explains both usage modes and what is returned, and the presence of an output schema means it doesn't need to detail return types.

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 description coverage is 100%; the input schema already explains the 'ids' parameter as 'Comma-sep ids; omit for index.' The description reiterates this but adds no significant new meaning beyond what the schema provides, so the baseline of 3 applies.

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 tool's function: 'Fetch Guild Wars 2 world (server) details by comma-separated IDs, or return the full index of world IDs'. It names the specific resource (worlds/servers) and the output contents (world name and population level), distinguishing it from sibling tools like items 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 Guidelines4/5

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

The description provides clear context for when to use the tool: for fetching world details by IDs or the full index. It doesn't explicitly name alternatives or exclusions, but given the tool is single-purpose and sibling tools are similarly specific, no further guidance is needed.

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