Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

attack_group

Queues a native attack on a visible hostile group and reads the squad’s active and queued orders so the attack follows existing commands.

Instructions

Queue a native attack on a visible hostile group. Read the squad's active and queued orders to follow it.

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>",
      "group_id": "<group_id>"
    },
    "name": "attack_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
virtualNo
group_idYes
squad_idYes
request_idYes
session_idYesCurrent session_id from get_state
replace_ordersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the action is queued rather than immediate and that the target must be visible and hostile, which is real value beyond structured fields. But it says nothing about the control/lease requirement, whether existing orders are overwritten, failure conditions, or what a successful queue returns.

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?

Two short sentences, front-loaded with the action and followed by the operating context. No filler, though the brevity leaves key parameters unexplained.

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

Completeness2/5

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

A 7-parameter mutation tool with no annotations and no output schema needs more than two sentences. The ambiguous replace_orders flag and virtual flag are the biggest gaps, along with no mention of the lease/session prereqs beyond what the schema descriptions already say.

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

Parameters2/5

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

Schema description coverage is only 29% (lease and session_id only). The description adds nothing about group_id, squad_id, virtual, or replace_orders. The 'queued orders' phrasing gestures at replace_orders but never clarifies whether true replaces the queue or appends to it, and virtual is entirely unaddressed.

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?

States a concrete verb and resource: 'Queue a native attack on a visible hostile group.' That distinguishes it from movement tools like move_npc_group. It does not explicitly contrast with any specific sibling, so it stops short of 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?

The second sentence hints at workflow ('Read the squad's active and queued orders to follow it'), implying this is used to issue an order the squad will then execute. There is no explicit when-to-use vs. alternatives, no statement of prerequisites such as needing control of the squad, and no exclusions.

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

Deploy Server

Other Tools