Skip to main content
Glama
Koodattu

wow-addon-api-mcp

by Koodattu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_event

Read-onlyIdempotent

Retrieve exact WoW frame event details, payload, and restrictions for a specified patch and channel.

Instructions

Get an exact WoW frame event, payload, and restrictions in one patch in the selected channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLiteral event name such as PLAYER_LOGIN or UNIT_AURA
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to restate safety. It usefully adds that the result is exact and includes payload and restrictions for a single patch, but it does not describe edge cases like 'latest' resolution or not-found 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 the resource, result contents, and scope with no filler or repetition. Every word earns its place.

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?

For a simple read-only lookup with fully documented parameters and safety annotations, the description covers what the tool returns and its scope. It could mention how 'latest' is handled in the version parameter, but the schema already covers that, so nothing critical is missing.

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%, with name, channel, and version all described. The description indirectly maps to channel/version via 'selected channel' and 'one patch' but adds no parameter-level detail beyond what the schema already provides.

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 exact resource (WoW frame event) and what is fetched (event, payload, restrictions), plus scoping to one patch and channel. This clearly differentiates it from sibling tools that target namespaces, datasets, APIs, resources, or migrations.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool instead of siblings like lookup_api, search_api, or compare_api. There are no alternatives, exclusions, or prerequisites mentioned, leaving the agent to infer usage from the word 'event' alone.

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