Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_building_workers

Change a building job's worker limit using a validated expected value to control how many workers are assigned to that worksite.

Instructions

Change a building job's worker limit using the same setter as the game. Read worksites for assigned workers and valid limits.

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>",
      "request_id": "<request_id>",
      "building_id": "<building_id>",
      "expected_max_workers": "<expected_max_workers>",
      "max_workers": "<max_workers>"
    },
    "name": "set_building_workers"
  }
}

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
request_idYes
session_idYesCurrent session_id from get_state
building_idYes
max_workersYes
expected_max_workersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden for a mutation tool. It says nothing about control-lease requirements, what happens when the expected value does not match, whether the change is reversible, or what a success/failure response looks like.

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?

Two short sentences, no filler, and the operation is front-loaded before the read hint. It is efficient but too terse to carry the semantics this tool needs.

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?

Six required parameters, no annotations, and no output schema make this a high-burden definition, yet it addresses only the happy-path intent. The concurrency-guard semantics and lease/session coupling are left entirely to inference.

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 coverage is only 33%, and the description explains none of the six parameters. The most consequential gap is the distinction between max_workers and expected_max_workers, which looks like an optimistic-concurrency guard but is never described in either the schema or the description.

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 gives a specific verb plus resource: 'Change a building job's worker limit', which separates it from neighbors like set_stockpile_amount or cheat_set_time. It does not explicitly name a sibling it supersedes, but the resource is unambiguous.

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?

'Read worksites for assigned workers and valid limits' implies a read-before-write precondition, which is useful implied guidance. However, no tool is named for that read, and there is no statement of when not to use this setter or what happens if the precondition is skipped.

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