Infection Free Zone MCP

Overview Schema Source Related Servers Discussions Admin

move_squad

Queue a native movement order 6–100 world units away, optionally replacing existing orders or moving a vehicle; pause first and retry with the same request_id.

Instructions

Queue a native move 6–100 world units away. Set replace_orders to override existing orders or move a vehicle. Pause first. Retry with the same request_id.

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": {
      "lease": "<lease>",
      "session_id": "<session_id>",
      "request_id": "<request_id>",
      "squad_id": "<squad_id>",
      "x": "<x>",
      "z": "<z>"
    },
    "name": "move_squad"
  }
}

Input Schema

Name	Required	Description
`x`	Yes
`z`	Yes
`lease`	Yes	Token returned by acquire_control
`squad_id`	Yes
`request_id`	Yes
`session_id`	Yes	Current session_id from get_state
`replace_orders`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavior: the move is queued rather than instantaneous, it is distance-constrained, and retries must reuse the same request_id (idempotency), plus a pause prerequisite. It stops short of covering failure modes, out-of-range rejection behavior, or whether the unit paths around obstacles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short imperative sentences, front-loaded with the core action and the distance constraint. The one weak sentence is the replace_orders clause, whose "or move a vehicle" tail reads ambiguously and costs a little clarity.

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?

For a 7-parameter mutating tool with no annotations and no output schema, the description covers prerequisites, idempotency, and a key range constraint, which is solid. It omits error behavior, what a successful queue returns (no output schema to fall back on), and control-lease implications beyond what the schema already documents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 29%, but the description compensates meaningfully: it explains request_id's retry semantics and replace_orders' override behavior, and it implicitly bounds x/z with the 6–100 unit constraint. Gaps remain for squad_id and for what a non-native versus native move distinction means, so it is not fully compensatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Queue a native move") and adds a concrete constraint, the 6–100 world-unit distance range, that is not in the schema. It does not differentiate from siblings like move_npc_group or attack_group, and the phrase "or move a vehicle" muddies what entity is actually being moved, which keeps it from a 5.

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?

"Pause first" gives an explicit prerequisite and "Set replace_orders to override existing orders" gives a conditional param-use rule, which is useful situational guidance. However, there is no statement of when to prefer this over move_npc_group or attack_group, and no mention of when the tool should not be used.

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

Deploy Server