Skip to main content
Glama
Sign In

Guild Wars 2

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Professions

professions
Read-onlyIdempotent

Professions.

Input Schema

NameRequiredDescriptionDefault
idsNo
langNo

Output Schema

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

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: -{
-  "id": {
-    "description": "Profession ID",
-    "type": "string"
-  },
-  "name": {
-    "description": "Profession name",
-    "type": "string"
-  }
-}
    • changedOutput schema / properties / items / items / type
      Previous value: -"object"New value: +"string"
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ids": "Guardian,Warrior"
+  },
+  {
+    "ids": "Mesmer",
+    "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 professions",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Profession ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Profession name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

D1.1/5.0
Behavior1/5

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

The description adds no behavioral context beyond what annotations already state (readOnlyHint, openWorldHint, etc.). Annotations indicate a safe, read-only operation, but the description fails to describe any additional constraints or behaviors.

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 short, but this is under-specification rather than conciseness. Every sentence should earn its place; here the single word fails to convey necessary information.

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 output schema exists and annotations are present, the description should still explain the tool's purpose and parameter usage. It is completely inadequate for a tool with two un-documented parameters.

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?

With 0% schema description coverage, the description must explain parameter meaning, but it does not. It does not mention 'ids' or 'lang' parameters at all.

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 single word 'Professions', which is a tautology that restates the tool name. It does not specify any action (e.g., 'list', 'get') or clarify what the tool does with professions.

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 guidance is provided on when to use this tool versus sibling tools. There is no mention of context, exclusions, or alternatives.

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