Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

wait_unpaused

Polls until the game is unpaused and no popup or UI pause is active, waiting up to a timeout so you can safely issue orders.

Instructions

Poll until the game is unpaused (and no popup/UI pause), up to a timeout. Useful right before issuing orders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait_unpaused"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_sNoMax wait seconds (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that this is a polling/blocking operation bounded by a timeout and that UI/popup pauses also count, but it never says what happens on timeout (error vs. silent return) or what the tool returns, which is the key behavioral question for a polling 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 the core behavior first and the practical tip second; nothing is padded or redundant.

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 simple one-parameter blocking tool this covers the essentials, but with no output schema and no annotations the failure mode on timeout is left unexplained, leaving the agent unsure whether to retry, check diagnose_pause, or treat the call as failed.

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 the single optional parameter already documents its range, default of 30, and meaning. The description's phrase 'up to a timeout' merely restates the schema without adding units, behavior at expiry, or guidance on picking a value.

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 ('Poll') and a specific target state ('game is unpaused'), and clarifies the condition includes popup/UI pause, which an agent could not otherwise infer. It does not name a sibling such as pause or diagnose_pause, so differentiation is implicit rather than explicit.

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?

'Useful right before issuing orders' gives one concrete when-to-use scenario, but there is no guidance on when not to use it, no mention of diagnose_pause as the alternative when the wait fails, and no advice on choosing a timeout value.

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