Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_stockpile_amount

Set a supported resource quantity in the shared stockpile while the game is paused. Pass the current amount as expected_amount to safely adjust stock levels.

Instructions

Set a supported resource in the shared stockpile while paused. Read resource_types for editable IDs and pass the current quantity as expected_amount.

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>",
      "expected_amount": "<expected_amount>",
      "amount": "<amount>"
    },
    "name": "set_stockpile_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
amountYes
session_idYesCurrent session_id from get_state
resource_idYes
expected_amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/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 does disclose the shared/multiplayer scope, the paused-state requirement, and the compare-and-swap intent of expected_amount, but says nothing about what happens on mismatch, error behavior, permission/lease failure, or whether the change is reversible.

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 tight sentences, front-loaded with the action and scoping condition, followed by the prerequisite pointer. No filler.

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?

For a 5-required-param mutation with no annotations and no output schema, the definition covers the critical concurrency and pause semantics but omits failure modes and return/confirmation behavior an agent would want before mutating shared state.

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 40% (only lease and session_id documented), yet the description adds real meaning for two undocumented params: resource_id must come from resource_types, and expected_amount is the pre-read current value. The amount parameter and resource_id format limits are still left implicit.

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 ("Set a supported resource in the shared stockpile") plus a scoping condition ("while paused"). It is distinguishable from cheat_add_resources by implying an absolute assignment rather than an increment, but it never names a sibling to sharpen the contrast.

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

Usage Guidelines4/5

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

Gives clear preconditions: the game must be paused, editable IDs come from resource_types, and expected_amount must be the current quantity. It lacks explicit exclusions (e.g., when to prefer cheat_add_resources), but the operational context is unambiguous.

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