Skip to main content
Glama
Koodattu

wow-addon-api-mcp

by Koodattu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_dataset_info

Read-onlyIdempotent

Resolve the WoW AddOn dataset for a selected channel and version, returning the upstream commit, entry counts, and archive coverage.

Instructions

Report the resolved WoW dataset for the selected channel, upstream commit, entry counts, and archive coverage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
    • addedInput schema / required
      Added value: +[
+  "channel",
+  "version"
+]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds the 'resolved' concept and lists what the report includes, but it does not explain resolution behavior, error cases, or response format.

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 compact sentence with no filler. It front-loads the action and resource, then efficiently lists the report contents, making every word useful.

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 two-parameter, read-only reporting tool, the description combined with the schema and annotations is nearly sufficient. It explicitly names the returned information (upstream commit, entry counts, archive coverage), though a bit more detail about what 'resolved' means and the response shape would make it fully complete.

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%, so the parameters are already well documented, including the channel enum and the version semantics. The description adds little beyond restating 'selected channel' and the notion of resolution, so it does not significantly augment the schema.

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

Purpose4/5

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

The description names a specific verb ('Report') and a specific resource ('resolved WoW dataset'), and enumerates the output dimensions: upstream commit, entry counts, and archive coverage. It is clear about what the tool does, but it does not explicitly distinguish itself from sibling tools like list_versions or diff_versions.

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?

The description provides no guidance on when to use this tool versus alternatives, and it does not mention any exclusions or related sibling tools. The usage context is only implied by the tool name and parameter schema, not stated.

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