Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cheat_scavenge_all

Mark every abandoned building on the map as scavenged in a single step. Requires a valid write lease and active session before issuing the order.

Instructions

Mark every abandoned building on the map as scavenged in one step. Requires the write lease.

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

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
session_idYesCurrent session_id from get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the key traits: this is a bulk mutation affecting every abandoned building, and it needs a write lease (an auth/control requirement). Missing are irreversibility, what happens to already-scavenged buildings, whether resources are granted, and any return/result behavior.

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?

Two short sentences, front-loaded with the action and followed by the precondition. Nothing is redundant or padded.

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 two-parameter tool with full schema coverage and no output schema, the description covers the action, scope, and the lease prerequisite adequately. The remaining gap is behavioral detail about side effects and post-call state, which matters for a bulk mutation but is a lesser omission than a missing purpose.

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 100% and both parameters are fully documented in the schema, so the baseline is 3. 'Requires the write lease' adds a little meaning by characterizing the lease as a write lease, but nothing is said about 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?

States a specific verb and resource ('Mark every abandoned building ... as scavenged') and makes the bulk scope explicit with 'in one step', which implicitly distinguishes it from the single-building sibling scavenge_building. It stops short of naming that sibling or clarifying the boundary with get_scavenge_plan, so an agent must infer the distinction.

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?

'Requires the write lease' is a precondition, not usage guidance. The description never says when to choose this bulk cheat over scavenge_building or when not to use it, and gives no caveats about running it after partial manual scavenging.

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