Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WARDOGS_HOMENoSets the directory where plans, screenshots, dataset cache, and browser profile are stored. Defaults to 'wardogs-mcp' in the user's home folder.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rulesA

The standing WARDOGS base-building ruleset: site limits, player movement facts, firing positions, fortification principles, walls and layers, gates, emplacements and builder quirks. Read this before planning a base.

list_buildablesA

List placeable pieces with id, cost, hp, c4, stack limit and footprint. Filter by kind: core, fortification, defence, support, vehicle, structure.

describe_buildableA

Full data for one piece: boxes, socket positions and kinds. Accepts id, label or a loose name like 'hesco small'.

data_refreshA

Re-extract the buildables dataset from wardogs.zone (cached 7 days otherwise).

plan_newC

Start an empty plan. world is null for the open pad (v1 only supports the open pad).

plan_statusB

Summary, supply cost, breakdown and validation issues for the current plan.

plan_piecesA

List pieces with key, position and yaw. Optional filter by id or label substring.

plan_codeB

The plan as the site's share string. Paste-able into the builder's draft or another tool.

plan_load_codeC

Replace the current plan with a site plan string (from plan_code, hub_import or the browser).

plan_saveA

Save the current plan to plans/.json in the writable home folder. Overwrites an existing plan of the same name.

plan_loadC

Load a plan saved with plan_save.

plan_listA

List saved plans in plans/.

undoB

Undo the last edit.

redoA

Redo the last undone edit.

place_fobA

Place the Forward Operating Base. Everything else must sit inside its 60 m square. Defaults to the origin.

placeA

Place one piece at (x, z) with yaw in degrees and optional height y. By default it snaps to the nearest compatible socket within snapRadius metres; set snap=false for free placement. parent limits snapping to one piece key.

wall_runA

Straight run of one piece type from (x1,z1) to (x2,z2) at socket pitch, long axis along the run. count overrides the piece count; skip lists indexes to leave out (for a gap).

ringB

Square ring of walls centred on (cx, cz), half metres from centre to each wall line. Optional gap on one side (north=-z, south=+z, east=+x, west=-x), gapWidth metres, and a gate piece placed in the gap.

perimeter_checkA

Count open side sockets per wall piece. A sealed wall shows every piece with exactly 2 open sockets (the outward and inward faces), corners included. 3 or more means a hole or a loose end. Optional filter by piece id.

stackB

Stack count more copies on top of piece key using its top socket (respects the stack limit).

moveC

Move a piece by a delta in metres and degrees.

set_poseB

Set a piece's absolute position and/or yaw.

removeB

Remove pieces by key.

remove_allB

Remove every piece, or every piece of one id.

browser_openA

Open (or focus) the builder in the MCP's own Chromium window. The first browser use downloads Chromium (a few hundred MB) if Playwright has not installed it yet. Sign in to Discord there once if you want hub_save.

browser_pushB

Render the current plan (or a given code) in the builder and read back the site's manifest.

browser_pullB

Adopt whatever the builder currently holds as the working plan (captures hand edits made in the window).

browser_readbackA

Read the builder's manifest, totals, status line and sign-in state without changing anything.

browser_screenshotA

Screenshot the builder window to plans/-.png. camera: 1..4 selects the builder's camera presets, 'f' frames the base.

browser_keyB

Press a key in the builder (camera 1-4, F frame, Tab cycle, Z/V toggles).

browser_closeA

Close the MCP's browser window.

hub_importB

Open another player's hub base (id or URL like https://wardogs.zone/loadouts/base/hub/a5f1729bb1) and adopt it as the working plan unless adopt=false.

hub_saveA

Push the current plan and open the site's save dialog with name and notes filled. Needs a Discord sign-in in the builder window; the user completes any captcha and clicks Save.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
rulesThe standing WARDOGS base-building ruleset.

TDQS

B3.4/5.0

Scored across 33 tools

Disambiguation4/5

Most tools target distinct resource+action pairs, and the detailed descriptions make even similar pairs (move vs set_pose as relative vs absolute, plan_pieces vs plan_status) easy to separate. A few pairs could trip up an agent though: plan_load_code vs plan_load (site string vs saved file), hub_import vs plan_load_code (both replace the plan from an external source), and browser_push vs browser_readback.

Naming Consistency3/5

Snake_case is used throughout and the plan_, browser_, and hub_ prefixes create strong group predictability. However, the word after the prefix alternates between noun (plan_status, plan_code, browser_readback) and verb (plan_save, plan_load, browser_push), and the bare tools mix verb-first (list_buildables, set_pose), noun-verb (data_refresh, wall_run), and imperative (undo, stack) styles.

Tool Count3/5

33 tools is heavy and exceeds the typical comfortable band, but the server genuinely spans several sub-domains: buildables catalog, plan lifecycle, geometry editing, persistence, hub sharing, and browser automation. Some fragmentation exists (wall_run and ring could be one pattern generator; the seven browser_* tools could be consolidated into fewer parameterized tools), so the count earns a middling score rather than a poor one.

Completeness5/5

The tool surface covers the full base-planning workflow with no dead ends: rules and buildable data, plan creation/query/serialization, every placement and transformation primitive, validation (plan_status, perimeter_check), persistence (plan_save/load/list), sharing (plan_code, hub_import/hub_save), and full browser interactivity including readback and screenshots. Every save has a corresponding load and every import has an export.

Maintenance

ActivityMaintained
ResponsivenessNo issues