Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cheat_add_resources

Add resources directly into the shared stockpile, bypassing scavenging entirely. Specify a resource ID and amount to top up colony supplies instantly, using the active write lease.

Instructions

Add resources straight into the shared stockpile, bypassing scavenging. 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>",
      "resource_id": "<resource_id>"
    },
    "name": "cheat_add_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
quantityNoAmount to add (default 100)
session_idYesCurrent session_id from get_state
resource_idYesExact ResourceID name, e.g. res_metal, res_bricks, res_drugs, res_ammo, eq_assault_rifle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: the operation skips normal gameplay flow (bypasses scavenging) and requires an authorization token (write lease). It does not say whether the effect is reversible, whether it interacts with session/achievement state, or what the result looks like, which is thin for an unannotated mutation tool.

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 with zero filler; the action and its bypass semantics come first and the auth prerequisite follows. Nothing is redundant with the title or restated.

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?

Parameters are fully covered by the schema, and the description supplies the two things the schema cannot: the gameplay bypass and the lease prerequisite. The only gap is that, with no output schema, an agent does not learn what the call returns or what happens on lease failure.

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% and the schema already documents lease (from acquire_control), session_id (from get_state), and resource_id with examples. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ('Add resources straight into the shared stockpile') and distinguishes the mechanism from the normal one ('bypassing scavenging'). An agent can tell this apart from cheat_scavenge_all, though it never names that sibling 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 phrase 'bypassing scavenging' implies when this is preferred over the scavenging path, and 'Requires the write lease' gives a hard prerequisite. However, it never explicitly says when to use this versus cheat_scavenge_all or any other cheat, and gives no exclusions.

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