Warcraft 3 MCP Server

Overview Schema Source Related Servers Discussions Admin

Read cameras

wc3_read_cameras

Extract and list all predefined cameras from a Warcraft III map file, including name, target, rotation, angle of attack, distance, and field of view.

Instructions

List predefined cameras (war3map.w3c) — name, target, rotation, angle of attack, distance, fov, etc.

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

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

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It implies read-only behavior by stating 'List', but does not disclose potential error conditions, permissions, or that it returns a list. Adequate for a simple read tool but could be more explicit.

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?

One concise sentence with no wasted words, front-loaded with the key action and data fields.

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 parameter and no output schema, the description is complete: it specifies what is read and what fields are included. Could mention the return format, but not essential.

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%, so the description adds no parameter information beyond what the schema already provides. The description does not mention the mapPath parameter, but the schema's description is sufficient.

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 the tool lists predefined cameras from a specific file and enumerates the data fields (name, target, rotation, etc.), distinguishing it from sibling tools like wc3_add_camera or wc3_delete_camera.

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 guidance on when to use this tool versus alternatives, though the purpose is clear from context and sibling names. A brief note about when to read vs. add/delete cameras would improve this dimension.

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