Skip to main content
Glama
Koodattu

wow-addon-api-mcp

by Koodattu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_enum

Read-onlyIdempotent

Retrieve a specific World of Warcraft enumeration with all its values and metadata for a chosen patch and game channel.

Instructions

Get an exact WoW enumeration and all values and metadata in one patch in the selected channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEnumeration name, with or without the Enum. prefix
channelYesGame channel; never inferred from a version number
versionYesPatch, full client build, build number, or latest within the selected channel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Game channel; never inferred from a version number",
+  "enum": [
+    "retail",
+    "forever"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / version / description
      Previous value: -"Retail patch, full client build, build number, or latest"New value: +"Patch, full client build, build number, or latest within the selected channel"
    • addedInput schema / properties / version / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "channel",
+  "version"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description only needs to add scoping context. It adds 'all values and metadata in one patch' but stops short of describing return shape or any special edge-case behavior.

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?

A single front-loaded sentence conveys resource, scope, and the channel/patch constraint with no filler or repetition.

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

Completeness4/5

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

With no output schema, the description's mention of 'all values and metadata' usefully signals the return content, and the 100% schema coverage covers the inputs. It could be slightly more explicit about the return structure, but it is complete enough for a read-only enum lookup.

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%, so all three parameters are already documented with descriptions, enums, and constraints (e.g., channel not inferred). The description repeats the patch/channel idea but adds no new parameter-level meaning beyond the schema.

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 names the specific verb, resource ('WoW enumeration'), and scope ('in one patch in the selected channel'), which clearly distinguishes it from comparison or lookup siblings like diff_versions and lookup_resource.

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 phrase 'exact ... in one patch in the selected channel' gives clear context for single-enumeration lookups, and the contrast with comparison/diff siblings is implied by the wording. However, it does not explicitly state when not to use this tool or name an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools