Warcraft 3 MCP Server

Overview Schema Source Related Servers Discussions Admin

Read terrain summary

wc3_read_terrain

Extract terrain summary from Warcraft III maps: tileset, ground/cliff tilesets, tilepoint dimensions, world size, and height/water ranges.

Instructions

Summarize war3map.w3e: tileset, ground/cliff tileset list, tilepoint dimensions, world size, and height/water ranges.

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_terrain"
  }
}

Input Schema

Name	Required	Description	Default
`mapPath`	Yes	Absolute path to the .w3x/.w3m map file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The name and description indicate a read-only operation ('read', 'summarize'), so no destructive hint needed. No annotations exist, but the description effectively communicates safety. Could add detail on permissions or map path requirements, but not critical.

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?

Single sentence, front-loaded with 'summarize', no wasted words. Each element listed is essential for understanding output.

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?

Lists specific output attributes, which is adequate for a summarization tool without an output schema. Could mention that the map file must be valid, but the required parameter implies that.

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 has 100% description coverage for the single parameter (mapPath). The description does not add further parameter detail, but the baseline is appropriate since the schema already documents it.

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 clearly states it summarizes the war3map.w3e terrain file and lists specific attributes (tileset, ground/cliff tileset list, tilepoint dimensions, world size, height/water ranges). This distinguishes it from sibling read tools that target other files.

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 description implies it should be used for reading terrain data, and sibling tools cover other resources (cameras, regions, etc.), providing clear context. No explicit when-not-to-use or alternative guidance, but the context is sufficient for differentiation.

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