Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_combat_estimate

Estimate combat outcomes for selected squads against a hostile group, including firepower, member counts, HP, and attack, retreat, or reinforcement advice.

Instructions

Heuristic combat estimate for chosen squads against one hostile group: firepower scores, member counts, HP, and advice (attack / retreat / need reinforcements).

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

Input Schema

NameRequiredDescriptionDefault
virtualNo
group_idYes
squad_idsNoSquads to send (default: all AI squads)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. The word 'heuristic' usefully signals that results are approximate rather than a full simulation, and it lists the returned fields, but it never states that the call is read-only and side-effect free, says nothing about whether squads must exist or be idle, and omits any cost or limit context (e.g., the 6-squad cap).

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 dense, front-loaded sentence with the purpose first and the promised outputs second. No filler, no restatement of the tool name.

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?

With no output schema, the description does a fair job of explaining what comes back (firepower, member counts, HP, advice). However, for a tool whose behaviour is opaque by default (no annotations), leaving the 'virtual' flag undefined and never confirming the call is a non-destructive read is a real gap.

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 only 33%: squad_ids is documented in the schema, while group_id and virtual are not. The description reinforces that a single hostile group is targeted and that squads are user-chosen, but the 'virtual' parameter is left entirely unexplained with no compensation in the text.

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 specific verb and resource: a heuristic combat estimate of chosen squads versus one hostile group, and enumerates the outputs (firepower scores, member counts, HP, attack/retreat/reinforce advice). This is clearly distinct from report-style siblings such as get_squads_report or get_enemy_report, though no sibling is named explicitly.

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 phrasing 'for chosen squads against one hostile group' implies the scenario (pre-combat planning) but gives no explicit when-to-use/when-not guidance and points to no alternative tool for deeper squad or enemy detail. An agent must infer the planning context.

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