Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

advance

Run the colony simulation at normal speed for a bounded 1–12 second window, then poll state and reapply pause at the deadline unless keep_running is set, enabling controlled live game time progression.

Instructions

Run the simulation at normal speed for at most 1–12 wall-clock seconds. Poll get_state. The bridge reapplies gameplay pause at the deadline unless keep_running is set. Background advance requires Unity to run in the background and explicit allow_background.

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

Input Schema

NameRequiredDescriptionDefault
leaseYesToken returned by acquire_control
secondsYes
session_idYesCurrent session_id from get_state
keep_runningNoLeave the game at normal 1x speed when the bounded window ends or the tracked order finishes. Use it while cooperating with a player who plays at 1x.
until_order_idNo
allow_backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the bounded wall-clock window, the side effect that gameplay pause is reapplied at the deadline unless keep_running is set, and the environment prerequisite for background advance. It omits failure modes on an expired lease and does not confirm whether the call blocks until the window elapses.

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?

Four dense sentences, front-loaded with the action and its bound before the operational caveats. No filler; every clause (poll target, pause reapplication, background prerequisite) changes how an agent would call the tool.

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 six-parameter, no-annotation, no-output-schema tool, the definition covers the key timing and pause semantics but leaves until_order_id unexplained and says nothing about what happens if the lease is stale or the session ends mid-window. Adequate to invoke, not complete enough to predict every outcome.

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 only 50%, and the description recovers meaning for two of the undocumented parameters — allow_background (Unity must be running in the background) and the behavioral effect of keep_running at the deadline. However, until_order_id is left completely undefined in both schema and description, and 'seconds' is only restated as wall-clock, so the gap is not fully compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('run the simulation') plus the exact operating mode and bound ('normal speed', 'at most 1–12 wall-clock seconds'), which makes it immediately distinguishable from sibling get_state (a read) and pause. An agent can tell what this does without opening the schema.

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?

It supplies concrete operational context: poll get_state afterwards, set keep_running when cooperating with a player at 1x, and only attempt background advance when Unity runs in the background with explicit allow_background. It never states an explicit exclusion ('do not use this when...') or names the pause sibling as the alternative for stopping time, so it stops short of full routing guidance.

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