Skip to main content
Glama
YElwiddi

Warcraft 3 MCP Server

by YElwiddi

Place a unit/item

wc3_place_unit

Place a unit or item on a Warcraft III map at specified coordinates using a 4-character raw code. Saves the edited map to a new file.

Instructions

Add a preplaced unit or item to the map at world coordinates (x, y). The type is a 4-char raw code, e.g. "ugho" (Ghoul), "hfoo" (Footman), or an item code. Saves to outPath, or ".edited." beside the source (pass the source path to overwrite in place).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapPathYesAbsolute path to the source .w3x/.w3m map file
typeYes4-char unit/item type code, e.g. "ugho"
xYesWorld X coordinate
yYesWorld Y coordinate
zNoWorld Z (height); default 0
facingNoFacing angle in degrees; default 270
playerNoOwner: 0-based player slot (0 = Player 1/Red). Default 0
scaleNoUniform scale; default 1
variationNoModel variation; default 0
hitpointsPercentNoHP as a percent, or -1 for default
manaPercentNoMana as a percent, or -1 for default
skinNoReforged skin code; defaults to `type`
outPathNoOutput map path. Defaults to "<map>.edited.<ext>".
Behavior4/5

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

Given no annotations, the description fairly conveys the tool is additive and outputs to a path, with overwrite behavior. Does not detail side effects like map modification limits or permissions.

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 sentences, no redundancy, efficiently communicates core function and key parameter details.

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?

Adequate for a tool with many parameters; schema fills details. Could mention typical use cases or prerequisites like map file existence, but overall sufficient.

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%, baseline is 3. Description adds value by explaining type code format and outPath overwrite, but does not elaborate on other parameters like z, facing, or player.

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 adds a preplaced unit/item to a map at coordinates, with examples of type codes ('ugho', 'hfoo'), distinguishing it from siblings like wc3_place_doodad or wc3_create_object.

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?

Provides usage note on overwriting source path and default output path, but lacks explicit guidance on when to use this tool over alternatives like wc3_modify_unit or wc3_create_object.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YElwiddi/warcraft-3-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server