Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_building_info

Retrieve a building’s type, state, scavenge flags, resource icons, and loot status—including squad progress and remaining crates—to decide whether to scavenge it.

Instructions

Read one building: type, state, scavenge flags, resource icons (Gun/Fuel/Drugs/Tools/Metal/Warehouse...), and loot details when a squad has already entered it (scavenge progress + remaining crates).

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>",
      "building_id": "<building_id>"
    },
    "name": "get_building_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesCurrent session_id from get_state
building_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.2/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 burden. It usefully discloses that loot details are conditional on a squad having entered the building, which is real behavioral information beyond schema, but it says nothing about read-only guarantees beyond the word "Read", permission/visibility requirements, or what happens for an unknown building_id.

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?

A single front-loaded sentence opens with the verb-resource pair and then appends the returned fields, with no filler. The parenthetical icon list is dense but earns its place as a hint at the return shape.

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 and no annotations, the description does reasonably well by enumerating the returned fields, but it leaves the provenance of building_id and error/edge-case behavior unstated. For a two-parameter read tool this is adequate but not complete.

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?

With schema coverage at 50%, only session_id is documented in the schema, so building_id depends on the description for meaning and it does not get it. The description never explains where building_id comes from (e.g., get_map_buildings or get_map_info) or what its format looks like, adding almost nothing over the parameter name.

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?

"Read one building" gives a specific verb and a singular resource, immediately distinguishing it from list-style siblings such as get_map_buildings. The enumeration of returned attributes (type, state, scavenge flags, resource icons, loot details) further pins down what the tool is for, 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?

Usage is only implied: an agent can infer this is the tool for inspecting a single building in depth. The conditional clause "when a squad has already entered it" explains payload variation rather than when to call the tool, and there is no guidance on choosing between this and get_map_buildings or get_scavenge_progress.

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