Skip to main content
Glama
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021

find_buildings_by_poi

Find map buildings by POI archetypes such as Gun, Fuel, Drugs, or Metal, using in-game OSM icon rules; optionally limit results by radius, coordinates, and scavengeable status.

Instructions

Find buildings by map resource icon: pass POI archetypes such as ["Gun","Fuel","Drugs","Metal"]. Uses the same OSM tag rules as the in-game icons.

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": {
      "session_id": "<session_id>",
      "poi": "<poi>"
    },
    "name": "find_buildings_by_poi"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
zNo
poiYes
limitNo
radiusNoRadius from HQ (default 2500)
session_idYesCurrent session_id from get_state
only_scavengeableNoOnly un-scavenged scavengeable buildings (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions OSM tag rules and in-game icons but does not disclose read-only behavior, result format, pagination, permissions, or how session_id and defaults affect the call.

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?

The description is two compact sentences with the core purpose front-loaded and useful examples embedded without wasted wording. It is appropriately sized for a search tool.

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?

For a seven-parameter search tool with no output schema and no annotations, the description is too thin. It omits alternatives, parameter behavior beyond poi, return expectations, and default/scope details that an agent needs to invoke it confidently.

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 43% across seven parameters, and the description only adds meaning for poi via archetype examples. It does not explain x/z, limit, radius, only_scavengeable, or the required session_id beyond what the schema already states.

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: finding buildings by map resource icon / POI archetypes. It gives concrete POI examples and mentions OSM tag rules, which helps distinguish the tool's domain, but it does not explicitly distinguish it from get_map_buildings or get_building_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance comparing this tool with alternatives such as get_map_buildings, nor any when-not-to-use guidance. The description implies the tool is for POI-based searches but leaves selection and prerequisites to inference.

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