Warcraft 3 MCP Server

by YElwiddi

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Delete region(s)

wc3_delete_region

Delete specified regions from a Warcraft III map using their id, name, or index, and save the map automatically.

Instructions

Remove the region(s) matched by id, name, or index. Saves the map.

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>",
      "select": "<select>"
    },
    "name": "wc3_delete_region"
  }
}

Input Schema

Name	Required	Description
`mapPath`	Yes	Absolute path to the .w3x/.w3m map file
`select`	Yes	Which region(s) to delete — provide one of id/name/index
`outPath`	No	Output map path. Defaults to "<map>.edited.<ext>" beside the source; pass the source path to overwrite in place.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions that the tool saves the map (side effect) but does not disclose permissions, return value, or behavior when no match is found. Minimal transparency beyond the basic action.

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?

Two concise sentences front-loaded with verb and resource. Every word is necessary; no redundancy or filler.

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

Completeness3/5

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

The tool has no output schema and no annotations. The description is adequate but leaves ambiguity about whether multiple regions can be deleted simultaneously (the select object allows only one criterion). Lacks details on outPath behavior (handled by schema) and return value.

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 parameters are already documented. The description adds the behavioral note 'Saves the map' but does not enhance understanding of parameters beyond what the schema provides. Baseline 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?

Description clearly states the tool removes regions matched by id, name, or index, and it distinguishes from related sibling tools like wc3_modify_region (modify) and wc3_add_region (add).

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?

The description implies usage for deleting regions but does not explicitly state when to use this tool versus alternatives like wc3_modify_region or wc3_delete_camera. No when-not or conditional guidance is provided.

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