Skip to main content
Glama
Sign In
Warcraft 3 MCP Server

Warcraft 3 MCP Server

by YElwiddi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read sound definitions

wc3_read_sounds

Extract sound definitions from a Warcraft 3 map file, listing variable names, file paths, and playback settings.

Instructions

List sound definitions (war3map.w3s) — variable name, file path, and playback settings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mapPath": "<mapPath>"
    },
    "name": "wc3_read_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapPathYesAbsolute path to the .w3x/.w3m map file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Without annotations, the description carries the full burden. It discloses the read-only nature, the file accessed, and the specific information returned. However, it does not mention behavior on missing files or error handling, which would improve transparency.

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 is front-loaded with the action and resource. No irrelevant information, and every word is necessary.

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 tool with one required parameter and no output schema, the description covers the essential information: what file, what data fields. It is sufficient for an agent to understand the tool's purpose and output.

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?

The input schema has 100% coverage with a clear parameter description. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 explicitly states it lists sound definitions from war3map.w3s, specifying the included fields (variable name, file path, playback settings). This clearly distinguishes it from sibling read tools like wc3_read_cameras or wc3_read_objects.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is given. The implication is to use this tool when you need to read sound definitions, but no alternatives or exclusions are mentioned. For a straightforward read tool, this is adequate but not exceptional.

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