Skip to main content
Glama
Sign In
Infection Free Zone MCP

Infection Free Zone MCP

by tianq021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cheat_set_time

Adjust the in-game day, hour, or time-speed multiplier with a valid write lease to control colony time progression.

Instructions

Set the in-game day/hour or the time-speed multiplier. 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>"
    },
    "name": "cheat_set_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNo
hourNo
leaseYesToken returned by acquire_control
speedNo
session_idYesCurrent session_id from get_state

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, the description carries the full burden, and it does disclose the write-lease authorization requirement, which the schema only hints at via the 'Token returned by acquire_control' parameter note. It does not explain partial-update behavior (whether setting only 'hour' leaves 'day' untouched), whether the lease is consumed or must be pre-acquired, or what happens on an invalid/expired lease.

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 action stated first and the prerequisite second; nothing is redundant or padded. Front-loading the effect before the lease requirement is the right ordering for an agent scanning for the operation.

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-parameter mutation tool with no annotations and no output schema, the definition covers purpose and authorization but leaves the semantics of the optional day/hour/speed trio underspecified. An agent can invoke it but may guess wrong about partial updates and field interaction.

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 only 40% (lease and session_id are documented), so day, hour, and speed rely on name and range alone. The description helps by expanding 'speed' into 'time-speed multiplier' and framing day/hour/speed as alternatives ('or'), but it adds no units, defaults, or interaction rules for those three fields.

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 uses a specific verb ('Set') with a concrete resource ('in-game day/hour or the time-speed multiplier'), so an agent knows exactly which game state this mutates. It does not name a sibling to contrast with (e.g., 'advance' or the other cheat_* tools), so differentiation is left to context.

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 prerequisite 'Requires the write lease' gives a real precondition for calling it, which is useful usage context. However, there is no explicit when-to-use guidance relative to siblings like 'advance' or the other cheat_* mutators, and no statement about which of day/hour/speed may be supplied together or in what combinations.

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