Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_infected_types

Break down nearby infected groups by variant, returning counts, HP ranges, tiers, and nearest squads for threat assessment and defense planning.

Instructions

Break down infected groups by variant: normal infected, infected dogs, suicide bombers (explosives), alpha infected, birds, giants and boosted variants. Returns counts, HP range, tier and which squads are nearest.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_infected_types"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusNoMax distance from HQ (default 4000)
include_lairsNoInclude lair groups (default true)
include_hiddenNoInclude undiscovered groups (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose the return payload (counts, HP range, tier, nearest squads), which is the most valuable part. However, it omits read-only framing, any indication of cost or rate limits, and the fact that results are scoped to a radius around HQ by default (4000), which materially affects what 'counts' mean.

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 sentences, front-loaded with purpose and followed by return contents; the long variant enumeration is dense but each item is informative. No filler or repetition.

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 query with fully documented optional parameters and no output schema, the description supplies the essential return-field information the structured data lacks. It falls short only on scoping defaults and any performance or safety notes, which an agent could still want.

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 description coverage is 100%, with each of the three optional parameters documented including defaults, so the baseline is 3. The description adds no parameter-specific meaning beyond the variant list, and it does not explain how radius or include_hidden interact with the reported counts.

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 states a specific verb and resource ('Break down infected groups by variant') and enumerates the variant categories, so an agent understands this is a per-type census of infected. It does not name or distinguish itself from close siblings like get_enemy_density or get_enemy_report, 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?

Usage is only implied: the enumeration of variants and the 'which squads are nearest' output suggest threat-assessment or targeting scenarios. There is no explicit when-to-use statement, no exclusion, and no routing to alternatives such as get_enemy_lairs despite a sibling of that name existing.

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